Was that last update on a rather old qemu e..g in Trusty?
In any way a bit more info on the system in use would be nice and to not wake
up this old bug too much if ok for you please create a new one with a reference
to this one being mentioned.
--
You received this bug notification because you
gmem.c:483: custom memory allocation vtable not supported
问题解决：
yum –y install gperftools-libs
c) reboot system
[root@l23-4-22 154363a6-13e0-4570-a1ef-53f2becacfbd]# rpm -ql gperftools-libs
/usr/lib64/libprofiler.so.0
/usr/lib64/libprofiler.so.0.4.5
/usr/lib64/libtcmalloc.so.4
/usr/lib6
** Package changed: qemu-kvm (Ubuntu) => qemu (Ubuntu)
** Changed in: qemu (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1491972
Title:
Memory trac
(Note, fix for this was acked upstream)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1491972
Title:
Memory tracing: glib/gmem.c: custom memory allocation vtable not
supported
To manage notificat
