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 692215 - add back support for configuring gmem, gslice, etc.
add back support for configuring gmem, gslice, etc.
Status: RESOLVED DUPLICATE of bug 687763
Product: glib
Classification: Platform
Component: general
unspecified
Other All
: Normal normal
: ---
Assigned To: gtkdev
gtkdev
Depends on:
Blocks:
 
 
Reported: 2013-01-21 16:57 UTC by Allison Karlitskaya (desrt)
Modified: 2013-01-21 17:03 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Allison Karlitskaya (desrt) 2013-01-21 16:57:27 UTC
Since we started using ctors, there was no way to do this since by the time main() runs it's already too late.

So here's an idea: we could come up with some symbol name like 'g_get_slice_allocator_config()' or something, and dlsym() that out of the process on libglib startup.  If the user provides that function, we call it to determine what our configuration should be.

I think it's probably good to continue to allow this (and Mozilla, for example, is quite upset to see it gone).  I also can't think of a better way to do it...

Thoughts?
Comment 1 Allison Karlitskaya (desrt) 2013-01-21 17:03:13 UTC

*** This bug has been marked as a duplicate of bug 687763 ***