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 752320 - g_mem_set_vtable with glib / gobject under MinGW
g_mem_set_vtable with glib / gobject under MinGW
Status: RESOLVED DUPLICATE of bug 701694
Product: glib
Classification: Platform
Component: gobject
2.44.x
Other Windows
: Normal normal
: ---
Assigned To: gtkdev
gtkdev
Depends on:
Blocks:
 
 
Reported: 2015-07-13 11:36 UTC by dejan.crnila
Modified: 2015-07-13 11:39 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description dejan.crnila 2015-07-13 11:36:27 UTC 
if app links to gobject and glib, it crashes if calling g_mem_set_vtable at start iin main function. The reason is that gobject dll already calls g_malloc inside dllmain startup, so it does not call original free / realloc functions.
Comment 1 Emmanuele Bassi (:ebassi) 2015-07-13 11:39:21 UTC 
Thanks for taking the time to report this.

This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

In particular, this isn't something limited to MingW, and we're thinking of deprecating the whole memory vtable override because it's impossible to support reliably — see bug 751592.

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