[tin-bugs] SIGSEGV in tin 2.4.4

[Urs Janßen]

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