Bug#833690: libgtk-3-0: SIGABRT in gmtp package

[Simon McVittie]

Control: reassign 833690 gmtp

On Sun, 07 Aug 2016 at 22:47:13 +0100, George B. wrote:
> I got a SIGABRT crash when using the gmtp package, but looking through
> backtrace I can only see GTK stuff

>From the backtrace, this is not necessarily GTK's fault.

This looks like memory corruption: something in that process (presumably
it is the gmtp process?) has corrupted the malloc data structures (for
instance by writing to freed memory). Later, GTK tries to allocate
some memory, and while allocating that memory for it, libc discovers
the corruption and aborts.

Unfortunately, it isn't possible to determine from that backtrace
whether the memory corruption in the past was caused by gmtp itself,
by GTK, or by some other library that gmtp uses.

The key backtrace entry is:

> #3  0x00007fb21f9d86b6 in malloc_printerr (action=3, str=0x7fb21fac88d7 "corrupted double-linked list", ptr=<optimized out>, ar_ptr=<optimized out>) at malloc.c:5004

I'm reasigning this to gmtp. Please send the information gathered by
"reportbug --template gmtp" (which will include the version number of gmtp
and the versions of all the libraries it uses). If you can reproduce
this crash by some particular sequence of actions, please send details
of that too.

Regards,
    S