[tin-bugs] SIGSEGV in tin 2.4.4

[Nigel Reed]

I compiled tin-2.4.5 with the same options as used for Ubuntu and here's the backtrace. Not sure if it helps.

Program terminated with signal SIGABRT, Aborted.
#0  __GI_raise (sig=sig at entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
50      ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) bt
#0  __GI_raise (sig=sig at entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#1  0x00007fb6fc815859 in __GI_abort () at abort.c:79
#2  0x000055ee1de0b614 in signal_handler (sig=<optimized out>) at ./signal.c:514
#3  <signal handler called>
#4  0x00007fb6fc8d0334 in __GI___clock_nanosleep (clock_id=<optimized out>, clock_id at entry=0, flags=flags at entry=0,
    req=req at entry=0x7fffea9f4d70, rem=rem at entry=0x7fffea9f4d70) at ../sysdeps/unix/sysv/linux/clock_nanosleep.c:78
#5  0x00007fb6fc8d6047 in __GI___nanosleep (requested_time=requested_time at entry=0x7fffea9f4d70,
    remaining=remaining at entry=0x7fffea9f4d70) at nanosleep.c:27
#6  0x00007fb6fc8d5f7e in __sleep (seconds=0, seconds at entry=2) at ../sysdeps/posix/sleep.c:55
#7  0x000055ee1de05242 in wait_message (sdelay=sdelay at entry=2, fmt=<optimized out>) at ./screen.c:173
#8  0x000055ee1ddd4b08 in write_newsrc_line (fp=0x55ee1ff54a20, line=0x55ee1ff50a80 "DOVE-Net.Unix") at ./newsrc.c:170
#9  0x000055ee1ddd5185 in write_newsrc () at ./newsrc.c:236
#10 0x000055ee1ddce377 in tin_done (ret=ret at entry=0, fmt=fmt at entry=0x0) at ./misc.c:618
#11 0x000055ee1de081d4 in select_quit () at ./select.c:1385
#12 0x000055ee1de09a01 in select_done () at ./select.c:1394
#13 selection_page (start_groupnum=<optimized out>, num_cmd_line_groups=<optimized out>) at ./select.c:387
#14 0x000055ee1dd8e09b in main (argc=<optimized out>, argv=<optimized out>) at ./main.c:436



> -----Original Message-----
> From: Urs Janßen <urs at tin.org>
> Sent: Thursday, January 28, 2021 10:28 AM
> To: Nigel Reed <nigel at nigelreed.net>
> Cc: tin-bugs at tin.org
> Subject: Re: [tin-bugs] SIGSEGV in tin 2.4.4
> 
> On Thu, Jan 28, 2021 at 03:54:23PM +0000, Nigel Reed wrote:
> > Hi all,
> >
> > I am viewing a message that had a future date.
> >
> > Message-ID: <60129A01.68.rmantiviru at endofthelinebbs.com>
> > Date: Tue, 12 Sep 2028 19:45:51 +0000
> >
> > When I hit F to followup I get the following:
> 
> I can't reproduce that with an freshly posted article on my local server with
> the mentioned date (modified it on spool).
> 
> I do not have access to the mentioned article and without knowing to which
> group it was posted it's close to impossible to find a server with read access
> with that article. so I can't use the original data for reproduction (and as the
> root cause may be something else than the date ...)
> 
> > tin: signal handler caught SIGSEGV signal (11).
> > tin 2.4.4 20191224 ("Millburn"): send a DETAILED bug report to
> > tin-bugs at tin.org<mailto:tin-bugs at tin.org>
> > Aborted (core dumped)
> 
> that's not that much info. if tin is compiled with debug infos (-g compiler flag;
> file /path/to/tin may show show something like "with debug_info, not
> stripped" or tin -V 2>&1 | grep FLAGS may reveal the used compiler flags)
> 
> passing tin and the core file to a debugger and asking for a stacktrace, e.g.
> 
> ~> gdb /usr/bin/tin core
> [...]
> (gdb) bt
> 
> or run it from within the ebugger and ask for a trace when it crashes should
> give us some useful info.
> 
> urs