Bug#819290: Stack trace with symbols

2016-03-27 Thread Michael Biebl
Control: tags -1 + pending patch Thanks for the debugging Yuriy Am 27.03.2016 um 04:14 schrieb Yuriy M. Kaminskiy: >> Regression by commit v228-745-gac9d396. Before that commit, >> device_setup_unit checked that sysfs is not NULL before calling >> path_equals(). >> I'd guess this commit should be

Bug#819290: Stack trace with symbols

2016-03-26 Thread Yuriy M. Kaminskiy
On 27.03.2016 05:01, Yuriy M. Kaminskiy wrote: On 27.03.2016 03:36, Kingsley G. Morse Jr. wrote: Hi Yuriy, OK, that all makes sense. Here's the full trace with symbols: #8 0x8017f167 in path_compare (a=, b=0x0) at ../src/basic/path-util.c:390 d = __PRETTY_FUNCTION__ = "p

Bug#819290: Stack trace with symbols

2016-03-26 Thread Yuriy M. Kaminskiy
On 27.03.2016 03:36, Kingsley G. Morse Jr. wrote: Hi Yuriy, OK, that all makes sense. Here's the full trace with symbols: #8 0x8017f167 in path_compare (a=, b=0x0) at ../src/basic/path-util.c:390 d = __PRETTY_FUNCTION__ = "path_compare" so, it assert() as `b == NULL` #9

Bug#819290: Stack trace with symbols

2016-03-26 Thread Kingsley G. Morse Jr.
Hi Yuriy, OK, that all makes sense. Here's the full trace with symbols: #0 0xb7769be0 in __kernel_vsyscall () (gdb) bt full #0 0xb7769be0 in __kernel_vsyscall () No symbol table info available. #1 0xb7444126 in kill () from /lib/i386-linux-gnu/i686/cmov/libc.so.6 No symbol table info availabl