-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 René Berber wrote: > Running Scribus with the debug enabled cygqt-mt-3.dll the program > works fine with no mutex failure message and using the latest Cygwin > snapshot. As mentioned in my reply to Brian, under gdb there are many > SIGSEGV signals received but continuing results in the same behaviour > as above: no problem. > > So there seems to be no regression, there must be something different > btw. the original build environment and my PC. I used the code (build > script, patches and original code) downloaded using setup.exe.
OK, we need to get back to this. Now that cygwin-1.5.19-4 is out, I'm seeing the same breakage with qt3-3.3.4: $ scribus Mutex init failure: Device or resource busy [splashscreen shows, gets as far as loading plugins, then:] Mutex init failure: Invalid argument [exits silently] $ convertall [this is a PyQt app. It exits silently also.] But not everything is affected apparently: $ xxdiff file1 file2 Mutex init failure: Device or resource busy [works, just like before] Mutex lock failure: Invalid argument Mutex unlock failure: Invalid argument Mutex destroy failure: Invalid argument 1) Something changed between 1.5.18 and the 20051207 snapshot to break qt3 threading. 2) It should not be necessary to have a debug library in order for ordinary programs to work. 3) A threaded Qt is required for many packages, including KDE, so disabling threading is not a viable option. Ideas? Yaakov -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFD4nhCpiWmPGlmQSMRAh9lAKCtvF9//J6zC4KWQsdJN9wiHPd95QCgxerD UYICx6yxX23jjUdxJAChwyg= =SImM -----END PGP SIGNATURE----- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
