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 702111 - Make g_setenv() assert() or warn() when used after threads started
Make g_setenv() assert() or warn() when used after threads started
Status: RESOLVED OBSOLETE
Product: glib
Classification: Platform
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gtkdev
gtkdev
Depends on:
Blocks:
 
 
Reported: 2013-06-12 15:40 UTC by Bastien Nocera
Modified: 2018-05-24 15:25 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Bastien Nocera 2013-06-12 15:40:04 UTC
To avoid the same sort of problem as in bug 701322, g_setenv() should warn if called after a glib thread was started.
This won't fix problems with applications that use non-glib threads, but should warn at least in this more common case.
Comment 1 Dan Winship 2013-06-12 16:32:57 UTC
attachment 197576 [details] [review] from bug 659326 does this, though it may have bitrotted some
Comment 2 Colin Walters 2013-06-12 16:54:20 UTC
One reverse dependency: https://bugs.freedesktop.org/show_bug.cgi?id=65681
Comment 3 GNOME Infrastructure Team 2018-05-24 15:25:55 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/glib/issues/715.