> It should print the backtrace with the location where the error happened.
Unfortunately, no. Sonne:/home/elfring/Projekte/Bau/systemd # systemctl stop systemd-udevd.service systemd-udevd-kernel.socket systemd-udevd-control.socket && gdb systemd-udevd … worker [5347] terminated by signal 11 (Segmentation fault) worker [5347] failed while handling '/devices/pci0000:00/0000:00:02.0/usb3/3-2/3-2:1.0' udev_monitor_send_device:/home/elfring/Projekte/systemd/lokal/src/libudev/libudev-monitor.c:770: passed device to netlink monitor 0x555555671520 ^CUnloaded link configuration context. [Inferior 1 (process 5339) exited normally] (gdb) bt full No stack. Sonne:~ # journalctl -xe … Jul 26 15:03:38 Sonne systemd-udevd[5347]: <audit-1701> auid=1000 uid=0 gid=0 ses=1 pid=5347 comm="systemd-udevd" exe="/home/elfring/Projekte/Bau/systemd/systemd-udevd" sig Jul 26 15:03:38 Sonne kernel: systemd-udevd[5347]: segfault at 438 ip 00007ffff6fefc78 sp 00007fffffffc6b0 error 4 in libc-2.21.so[7ffff6fa7000+196000] … Do I need to be more concerned about an "error 4"? Regards, Markus _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
