Bug 38836

Summary:	mutt get a SIGSEGV while sorting mailbox
Product:	Gentoo Linux	Reporter:	Fernand Albarracin <fernand8>
Component:	Current packages	Assignee:	Net-Mail Packages <net-mail+disabled>
Status:	RESOLVED UPSTREAM
Severity:	critical
Priority:	High
Version:	unspecified
Hardware:	x86
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---
Attachments:	GDB session with some comments

Description Fernand Albarracin 2004-01-20 11:34:37 UTC

I receive a lot of spam. These are written in the "=spam" mailbox (mbox format).
Sometimes, it looks like Mutt crashes when it sorts the mailbox containing
these messages.

I've searched on the Web and found a lot of similar reports :
http://groups.yahoo.com/group/mutt-dev/message/13096
http://groups.yahoo.com/group/mutt-dev/message/13107
http://bugs.guug.de/db/11/1124.html
http://groups.yahoo.com/group/mutt-dev/message/17436
http://bugs.guug.de/db/14/1443.html


Reproducible: Sometimes
Steps to Reproduce:
1. the spam mailbox is open
2. a message arrives in this mailbox (fetchmail)
3. I suppose that mutt reads the mailbox, then sorts it (thread mode),

Actual Results:  
Sorting mailbox...
Program received signal SIGSEGV, Segmentation fault.

Please have a look at the attachment.

Expected Results:  
Well, it shouldn't crash. At this point, I think Mutt simply re-displays
the mailbox content.

I'm using the latest (stable) Mutt ebuild. In order to get the trace, I used the
following command :

FEATURES="noclean nostrip" CFLAGS="-g" emerge mutt

It is net-mail/mutt-1.5.4-r1.

System information:

# emerge info
Portage 2.0.49-r21 (default-x86-1.4, gcc-3.2.3, glibc-2.3.2-r3, 2.4.23)
=================================================================
System uname: 2.4.23 i686 AMD Athlon(tm) MP 1800+
Gentoo Base System version 1.4.3.10p1
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CFLAGS="-march=athlon-mp -Os -fomit-frame-pointer -pipe"
CHOST="i686-pc-linux-gnu"
COMPILER="gcc3"
CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config
/usr/kde/3/share/config /usr/share/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d"
CXXFLAGS="-march=athlon-mp -Os -fomit-frame-pointer -pipe"
DISTDIR="/mnt/shared/distfiles"
FEATURES="autoaddcvs ccache sandbox"
GENTOO_MIRRORS="http://www.mirror.ac.uk/sites/www.ibiblio.org/gentoo
http://mirrors.serveftp.org/gentoo
http://distro.ibiblio.org/pub/Linux/distributions/gentoo"
MAKEOPTS="-j2"
PKGDIR="/mnt/shared/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY=""
SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage"
USE="3dnow X alsa apm avi berkdb crypt cscope doc dvd encode foomaticdb gdbm gif
gnome gphoto2 gtk gtk2 gtkhtml guile imlib jpeg libg++ libwww mad mbox mikmod
mmx mozilla moznocompose moznoirc moznomail mozsvg mpeg ncurses nocardbus
oggvorbis opengl oss pam pdflib perl plotutils png python quicktime readline sdl
spell sse ssl tcltk tcpd tetex tiff truetype x86 xml xml2 xmms xv zlib"

Comment 1 Fernand Albarracin 2004-01-20 11:35:34 UTC

Created attachment 24141 [details]
GDB session with some comments

Comment 2 Aron Griffis (RETIRED) gentoo-dev

2004-02-11 12:51:58 UTC

This bug is not going to be solved within Gentoo.  You've done a really nice job generating a backtrace with -O0, though!  You should send this bug upstream and see what they do with it (using the "flea" program that comes with mutt)