Yeah, we've all been sort of aware of this for some time. I've abused it to the fact where I know that malloc and g_new / free and g_free will *always* be the same since a specific glib version.
I think removing all the code is fine. On Fri, Jun 26, 2015 at 8:38 PM, Alexander Larsson <al...@redhat.com> wrote: > So, I just tried to use the memory profiler in glib, and I crashes > really early because the gobject constructor (gobject_init_ctor) calls > g_malloc before main() is reached. > > This means g_mem_set_vtable() is impossible to use. I don't necessarily > think this is all that bad. Honestly we should never have made it a > vtable (one extra vfunc per malloc...) and instead do memory profiling > etc the "normal" way, i.e. LD_PRELOAD something with malloc > interceptors. Maybe we should just remove all this code and keep > g_mem_set_vtable as a dummy function that prints a deprecation warning? > _______________________________________________ > gtk-devel-list mailing list > gtk-devel-list@gnome.org > https://mail.gnome.org/mailman/listinfo/gtk-devel-list -- Jasper _______________________________________________ gtk-devel-list mailing list gtk-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/gtk-devel-list
