[stgt] segfault in tgtd

Ryusuke Konishi konishi.ryusuke at lab.ntt.co.jp
Fri Jan 24 09:58:52 CET 2014

Hi Alban,
On Fri, 24 Jan 2014 14:27:37 +0900 (JST), FUJITA Tomonori wrote:
> On Tue, 21 Jan 2014 11:29:26 +0000
> Alban Rrustemi <alban at fonleap.com> wrote:
>> We've been evaluating the tgt version 1.0.38 on a 64bit Linux kernel
>> (version 3.2.0-39-generic) in an Ubuntu installation. Occasionally, we
>> get a segmentation fault in tgtd and it's not clear what went wrong or
>> how to get more information in order to investigate the root cause.
>> All I get to see is lines like the ones below in the kernel log:
>> Jan 21 07:03:40 test-machine kernel: [2744939.501604] tgtd[12887]:
>> segfault at 0 ip 00000000004076aa sp 00007fffe0bcfa40 error 6 in
>> tgtd[400000+43000]
>> Jan 21 07:04:04 test-machine kernel: [2744963.554504] init: tgt main
>> process (12887) killed by SEGV signal
>> Is there any documentation out there or any other type of information
>> on some tgt diagnostics I could use to investigate this?
> Unfortunately, I can't tell much with the above. Did you see anything
> in syslog? Anything (workload, etc) changed right before the crash?

Was there a core file in the root directory or at your home directory

If it exists, you can get backtrace of the segmentation fault with
gdb, and it may give very helpful information to narrow down the root
cause of the problem.

Usually, we use gdb for this purpose as follows:

 # gdb tgtd /core.12345
 (gdb) bt

You may need to install *-dbg package if your tgt has no symbol

For more details, please see instructions described in the distro
sites like below:

 [1] https://wiki.ubuntu.com/Backtrace 
 [2] https://wiki.ubuntu.com/DebuggingProcedures

Ryusuke Konishi
To unsubscribe from this list: send the line "unsubscribe stgt" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

More information about the stgt mailing list