[Bug 1491972] Re: glib/gmem.c: custom memory allocation vtable not supported

Serge Hallyn 1491972 at bugs.launchpad.net
Fri Sep 4 15:21:37 UTC 2015


Hm, this comes from vl.c:2989 (in git) calling
g_mem_set_vtable(&mem_trace), which has been around since 2011 to add
tracepoints for g_malloc/g_free.

https://github.com/GNOME/glib/blob/master/glib/gmem.c shows that this
function is deprecated.

This means that tracing won't work right, but should otherwise be
innocuous.  Will see what upstream thinks about it.


** Changed in: qemu-kvm (Ubuntu)
   Importance: Undecided => Low

** Summary changed:

- glib/gmem.c: custom memory allocation vtable not supported
+ Memory tracing: glib/gmem.c: custom memory allocation vtable not supported

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1491972

Title:
  Memory tracing: glib/gmem.c: custom memory allocation vtable not
  supported

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1491972/+subscriptions



More information about the Ubuntu-server-bugs mailing list