ronnie sahlberg schrieb: > Since it is reproducible, can you run it under gdb and get a backtrace? I'm not sure what is the correct approach to debug tgtd in gdb. But simply running a debugger against tgtd (with an initiator connected) can make it segfault: (gdb) attach 9348 Attaching to process 9348 Reading symbols from /usr/sbin/tgtd...done. Using host libthread_db library "/lib/tls/libthread_db.so.1". Reading symbols from /usr/lib/i686/cmov/libcrypto.so.0.9.8...done. Loaded symbols for /usr/lib/i686/cmov/libcrypto.so.0.9.8 Reading symbols from /lib/tls/libpthread.so.0...done. [Thread debugging using libthread_db enabled] [New Thread 1875564768 (LWP 9348)] [New Thread 1758104496 (LWP 9378)] [New Thread 1766493104 (LWP 9377)] [New Thread 1774881712 (LWP 9376)] [New Thread 1783270320 (LWP 9375)] [New Thread 1791658928 (LWP 9374)] [New Thread 1800047536 (LWP 9370)] [New Thread 1808436144 (LWP 9369)] [New Thread 1816824752 (LWP 9368)] [New Thread 1825213360 (LWP 9367)] [New Thread 1833601968 (LWP 9366)] [New Thread 1841990576 (LWP 9359)] [New Thread 1850379184 (LWP 9358)] [New Thread 1858767792 (LWP 9357)] [New Thread 1867156400 (LWP 9356)] [New Thread 1875545008 (LWP 9355)] Loaded symbols for /lib/tls/libpthread.so.0 Reading symbols from /lib/tls/libc.so.6...done. Loaded symbols for /lib/tls/libc.so.6 Reading symbols from /lib/tls/libdl.so.2...done. Loaded symbols for /lib/tls/libdl.so.2 Reading symbols from /usr/lib/libz.so.1...done. Loaded symbols for /usr/lib/libz.so.1 Reading symbols from /lib/ld-linux.so.2...done. Loaded symbols for /lib/ld-linux.so.2 0x6fd92679 in epoll_wait () from /lib/tls/libc.so.6 (gdb) cont Continuing. Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 1875564768 (LWP 9348)] __cmd_done (target=0x0, cmd=0x9ee9748) at target.c:864 864 err = target->bst->bs_cmd_done(cmd); -- Tomasz Chmielewski http://wpkg.org |