Re: [libvirt] [PATCH] Fix building with -Og

On 03.06.2016 13:52, Peter Krempa wrote: Well, this is not a result of a bleeding edge compiler. This occurs on my (now ancient) compiler too. I got to the same result. Martin and me were trying to get a sensible backtraces instead of the following ones: Condvar #0 (0x0x7f97580010c8) first referenced by: /home/zippy/tmp/mutrace.git/.libs/libmutrace.so(pthread_cond_init+0x122) [0x7f97b92946f0] /home/zippy/work/libvirt/libvirt.git/src/.libs/libvirt.so.0(virCondInit+0x1d) [0x7f97b8757a27] /home/zippy/work/libvirt/libvirt.git/src/.libs/libvirt_driver_qemu.so(+0xb87d0) [0x7f978679c7d0] /home/zippy/work/libvirt/libvirt.git/src/.libs/libvirt_driver_qemu.so(qemuMonitorOpen+0x12e) [0x7f978679cbc8] /home/zippy/work/libvirt/libvirt.git/src/.libs/libvirt_driver_qemu.so(+0x99a84) [0x7f978677da84] /home/zippy/work/libvirt/libvirt.git/src/.libs/libvirt_driver_qemu.so(+0x9d4e1) [0x7f97867814e1] /home/zippy/work/libvirt/libvirt.git/src/.libs/libvirt.so.0(+0xe6c4c) [0x7f97b8757c4c] /lib64/libpthread.so.0(+0x7434) [0x7f97b54c6434] (notice those anonymous static functions which makes this output unreadable) This is an output from a tool that analyses mutex/condvar congestions: http://git.0pointer.net/mutrace.git Cheers. Michal