[tin-bugs] tin: signal handler caught SIGSEGV signal (11)

Olaf Schneider olaf at schneider-wsw.de
Sun Apr 9 12:32:52 CEST 2017


Dear Tin developers,

after updating some packages on my openSUSE tumbleweed system I get an
error right after startup of tin:

rtin: signal handler caught SIGSEGV signal (11).
rtin 2.4.1 20161224 ("Daill") [UNIX]: schicken Sie einen DETAILLIERTEN
Fehlerbericht an tin-bugs at tin.org

I recompiled tin with debug option (td-conf.out and config.log attached)
and run it via "tin -D 63" resulting in:

tin: signal handler caught SIGSEGV signal (11).
tin 2.4.1 20161224 ("Daill") [UNIX]: schicken Sie einen DETAILLIERTEN
Fehlerbericht an tin-bugs at tin.org Abgebrochen (Speicherabzug
geschrieben)

The only written debug file is MALLOC (see attachment). Running gdb on
the core dump tells:

Program terminated with signal SIGABRT, Aborted.
#0  __GI_raise (sig=sig at entry=6)
at ../sysdeps/unix/sysv/linux/raise.c:51

Any idea, what is going wrong there?

Kind regards, Olaf
-------------- next part --------------
A non-text attachment was scrubbed...
Name: MALLOC
Type: application/octet-stream
Size: 1256 bytes
Desc: not available
URL: <http://lists.tin.org/pipermail/tin-bugs/attachments/20170409/765f40ce/attachment-0002.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: td-conf.out
Type: application/octet-stream
Size: 77333 bytes
Desc: not available
URL: <http://lists.tin.org/pipermail/tin-bugs/attachments/20170409/765f40ce/attachment-0003.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: config.log
Type: text/x-log
Size: 37352 bytes
Desc: not available
URL: <http://lists.tin.org/pipermail/tin-bugs/attachments/20170409/765f40ce/attachment-0001.bin>


More information about the tin-bugs mailing list