Re: [libvirt] Segfault in virDomainObjListSearchName when listing domains (qemu backend)
I'm still seeing segfaults in virDomainObjListSearchName, expect now they're
no longer easily reproducible:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffeffff710 (LWP 5446)]
0x00007ffff7411746 in __strcmp_sse42 () from /lib64/libc.so.6
Missing separate debuginfos, use: debuginfo-install glibc-2.11.2-1.x86_64 nss-
softokn-freebl-3.12.6-2.fc12.1.x86_64 openssl-1.0.0a-1.fc12.x86_64
(gdb) bt
#0 0x00007ffff7411746 in __strcmp_sse42 () from /lib64/libc.so.6
#1 0x00007ffff7ac9d79 in virDomainObjListSearchName (payload=0x7fffdc004060,
name=<value optimized out>, data=0x7fffd8009850) at conf/domain_conf.c:367
#2 0x00007ffff7ab476e in virHashSearch (table=0x6f59a0, iter=0x7ffff7ac9d50
<virDomainObjListSearchName>, data=0x7fffd8009850) at util/hash.c:582
#3 0x00007ffff7ac9d33 in virDomainFindByName (doms=<value optimized out>,
name=0x7fffd8009850 "testserver-d") at conf/domain_conf.c:377
#4 0x00000000004430f6 in qemudDomainLookupByName (conn=0x7fffe00009f0,
name=0x7fffd8009850 "testserver-d") at qemu/qemu_driver.c:4166
#5 0x00007ffff7af95cd in virDomainLookupByName (conn=0x7fffe00009f0,
name=0x7fffd8009850 "testserver-d") at libvirt.c:2169
#6 0x0000000000423e64 in remoteDispatchDomainLookupByName (server=<value
optimized out>, client=<value optimized out>, conn=0x7fffe00009f0, hdr=<value
optimized out>, rerr=0x7fffefffec70,
args=<value optimized out>, ret=0x7fffefffebc0) at remote.c:2030
#7 0x0000000000426a91 in remoteDispatchClientCall (server=<value optimized
out>, client=0x7ffff0095590, msg=0x7ffff00520e0) at dispatch.c:506
#8 0x0000000000426e43 in remoteDispatchClientRequest (server=0x6e3cd0,
client=0x7ffff0095590, msg=0x7ffff00520e0) at dispatch.c:388
#9 0x0000000000417ed8 in qemudWorker (data=0x7ffff00008d8) at libvirtd.c:1568
#10 0x00007ffff7878a3a in start_thread () from /lib64/libpthread.so.0
#11 0x00007ffff73d377d in clone () from /lib64/libc.so.6
#12 0x0000000000000000 in ?? ()
(gdb)
This one happened when starting up a previously defined domain.
Restarting libvirtd and trying the same thing again resulted in a running
domain, with no crashes anywhere... (There were no changes in configuration or
installed software between the two attempts.)
Guido