After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 631211 - gtk programs crash on startup if glib is compiled with --enable-threads on Cygwin
gtk programs crash on startup if glib is compiled with --enable-threads on Cy...
Status: RESOLVED OBSOLETE
Product: glib
Classification: Platform
Component: gthread
unspecified
Other Cygwin
: Normal blocker
: ---
Assigned To: gtkdev
gtkdev
Depends on:
Blocks:
 
 
Reported: 2010-10-03 07:21 UTC by Michiel de Hoon
Modified: 2012-07-06 01:24 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Michiel de Hoon 2010-10-03 07:21:02 UTC 
If glib is compiled with --enable-threads on Cygwin, then most (if not all) GTK programs crash on startup with a segmentation fault. This includes the GTK test programs. If glib is compiled with --enable-threads=no, then the GTK programs seem to work correctly. I have noticed this behavior with all recent versions of glib; I don't recall seeing a glib version that doesn't cause GTK crashes if glib is compiled with --enable-threads. I'd be happy to provide more information but I am a bit lost as to where to start to solve this bug.
Comment 1 Matthias Clasen 2012-07-06 01:24:51 UTC 
I don't think this applies to current glib anymore; the threading system has been entirely rewritten since then. Please reopen if you still see this problem with 2.32