On Fri, Dec 22, 2017 at 09:52:33AM +0100, Holger Schranz wrote:
etcsvms1:/kvm/CS8200/M5 # coredumpctl gdb libvirtd PID: 10728 (libvirtd) UID: 0 (root) GID: 0 (root) Signal: 11 (SEGV) Timestamp: Fri 2017-12-22 09:28:39 CET (18min ago) Command Line: /usr/local/sbin/libvirtd -d Executable: /usr/local/sbin/libvirtd Control Group: / Slice: -.slice Boot ID: 01603763bc784c7380e310d5eea124d6 Machine ID: 89c660865c00403a9bacef32b6828556 Hostname: etcsvms1 Coredump: /var/lib/systemd/coredump/core.libvirtd.0.01603763bc784c7380e310d5eea124d6.10728.1513931319000000.xz Message: Process 10728 (libvirtd) of user 0 dumped core.
Core was generated by `/usr/local/sbin/libvirtd -d'. Program terminated with signal SIGSEGV, Segmentation fault. #0 virStorageFileReportBrokenChain (errcode=2, src=src@entry=0x7f0d4004ac40, parent=0x7f0d4004ac40) at storage/storage_source.c:422 422 unsigned int access_user = src->drv->uid; [Current thread is 1 (Thread 0x7f0d525ab700 (LWP 10729))] Missing separate debuginfos, use: zypper install
(gdb)
You've not given a full stack trace here - just the top most frame. Can you do it again and run (gdb) thread apply all backtrace full Regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|