> > Is there any update so far? I’m asking because I’m still getting > segmentation faults and hang-ups on termination of libvirtd (using the > newest version of libvirt). > > Example for a hang-up: > ➤ bt > #0 0x000003fffca8df84 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 > #1 0x000003fffdac29ca in virCondWait (c=<optimized out>, m=<optimized out>) at ../../src/util/virthread.c:154 > #2 0x000003fffdac381c in virThreadPoolFree (pool=<optimized out>) at ../../src/util/virthreadpool.c:290 > #3 0x000003fffdbb21ae in virNetServerDispose (obj=0x1000cc640) at ../../src/rpc/virnetserver.c:803 > #4 0x000003fffda97286 in virObjectUnref (anyobj=<optimized out>) at ../../src/util/virobject.c:350 > #5 0x000003fffda97a5a in virObjectFreeHashData (opaque=<optimized out>, name=<optimized out>) at ../../src/util/virobject.c:591 > #6 0x000003fffda66576 in virHashFree (table=<optimized out>) at ../../src/util/virhash.c:305 > #7 0x000003fffdbaff82 in virNetDaemonDispose (obj=0x1000cc3c0) at ../../src/rpc/virnetdaemon.c:105 > #8 0x000003fffda97286 in virObjectUnref (anyobj=<optimized out>) at ../../src/util/virobject.c:350 > #9 0x0000000100026cd6 in main (argc=<optimized out>, argv=<optimized out>) at ../../src/remote/remote_daemon.c:1487 > > And segmentation faults happen for RPC jobs that are still running. > There has been zero of my cycles spent thinking about this. Partially because I'm busy in other areas, partially because I know Daniel is planning changes in libvirtd (https://www.redhat.com/archives/libvir-list/2018-May/msg01307.html), and partially because I'm not sure I have a {reliable|simple} reproducer (at least I don't recall). I do still have various branches in various states of disarray that are way behind current head (easy to happen it seems lately). John -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list
