On Sat, 2015-06-27 at 05:38 +0200, Alexander Larsson 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
On Fri, 2015-06-26 at 20:50 -0700, Jasper St. Pierre wrote:
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
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
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
On Fri, Jun 26, 2015 at 8:50 PM, Jasper St. Pierre jstpie...@mecheye.net
wrote:
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
