Bug#561279: udev: Crash location and first-level cause

2009-12-25 Thread Kay Sievers
srv:~# udevadm info custom logging function 0x160e010 registered selinux=0 calling: info Segmentation fault This was likely caused by using a va_list twice. This is expected to fix it: http://git.kernel.org/?p=linux/hotplug/udev.git;a=commitdiff;h=d5a01cb8b31bd0791d1617c56d4c669a02018bd7

Bug#561279: udev: Crash location and first-level cause

2009-12-24 Thread Stephen Kitt
Package: udev Version: 149-1 Severity: normal Hi, I can reliably reproduce this bug too, on two RAID1 devices managed by md. The bug also occurs with a non-stripped build of udevadm; the crash occurs at line 393 of udevadm-info.c; here’s the gdb session: (gdb) run Starting program: