Bugzilla Bug 120981

When using IMAPSTATUS in the configuration entry 'index-format' (instead of,
e.g., FULLSTATUS) pine crashes upon entering some (IMAP-) folder.  (Does not
happen with all folders.)  The Konsole "Shell session" exits with signal 6.
When using a textconsole, I get "*** glibc detected *** double free or
corruption (!prev): 0x0000000000a9a750 ***".

Debug output (-d 9 option) does not give any clues except that the crash
happens after/durig sorting of the messages in the folder. (Debug output not
given because it contains too much personal info.)

The thread I started on comp.mail.pine starts with the post with
Message-ID: <Pine.LNX.4.64.0601262306560.7297@ybpnyubfg>.

'emerge --info' output:

Portage 2.0.54 (default-linux/amd64/2005.0, gcc-3.4.4, glibc-2.3.5-r2,
2.6.15-gentoo-r1 x86_64)
=================================================================
System uname: 2.6.15-gentoo-r1 x86_64 AMD Athlon(tm) 64 Processor 3200+
Gentoo Base System version 1.6.14
distcc 2.18.3 x86_64-pc-linux-gnu (protocols 1 and 2) (default port 3632)
[disabled]
dev-lang/python:     2.4.2
sys-apps/sandbox:    1.2.12
sys-devel/autoconf:  2.13, 2.59-r6
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1
sys-devel/binutils:  2.16.1
sys-devel/libtool:   1.5.22
virtual/os-headers:  2.6.11-r2
ACCEPT_KEYWORDS="amd64"
AUTOCLEAN="yes"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-march=athlon64 -O3 -ftracer -funit-at-a-time -fforce-addr -fpeel-loops
-funswitch-loops -pipe"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.4/env
/usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config
/usr/lib/X11/xkb /usr/share/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/texmf/web2c /etc/env.d"
CXXFLAGS="-march=athlon64 -O3 -ftracer -funit-at-a-time -fforce-addr
-fpeel-loops -funswitch-loops -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig distlocks sandbox sfperms strict"
GENTOO_MIRRORS="http://distfiles.gentoo.org
http://distro.ibiblio.org/pub/linux/distributions/gentoo"
LANG="en_US.UTF-8"
LC_ALL=""
LINGUAS="en_US nl"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage"
USE="amd64 7zip X aac aalib alsa arts audiofile avi bash-completion berkdb
bitmap-fonts blas bzip2 cdr crypt cups curl dhcp dvd dvdr dvdread eds emboss
encode esd exif fam ffmpeg flac foomaticdb fortran gcj gd gif gmp gpm gstreamer
gtk2 hal idn ieee1394 imagemagick imap imlib java javascript jpeg justify kcal
kde kdepim largeterminal lcms ldap libcaca libwww lm_sensors logitech-mouse lzw
lzw-tiff mad mime mng mozilla mozsvg mp3 mpeg mplayer mppe-mppc ncurses network
nls nodrm nvidia ogg oggvorbis opengl pam pcre pdf pdflib perl pic plotutils
png ppds python qt quicktime readline real recode samba sdl sensord slang spell
ssl subversion svg symlink tcpd tetex theora tiff truetype truetype-fonts type1
type1-fonts udev unicode usb userlocales visualization vorbis wifi wmf xine
xml2 xpm xprint xv xvid xvmc zlib linguas_en_US linguas_nl userland_GNU
kernel_linux elibc_glibc"
Unset:  ASFLAGS, CTARGET, LDFLAGS

I compiled the unpatched sources and those work without a glitch with
IMAPSTATUS. Some functionality is lost however.

So, it must be one of the patches.

(N.B.: Eduardo Chappa is also looking at this.)

(In reply to comment #1)
> (N.B.: Eduardo Chappa is also looking at this.)
> 
Eduardo Chappa has identified the problem and updated his patches.
If necessary, make changes to the ebuild. I suggest a version bump to -r2.

Erik

I can do this tonight, or tomorrow. I'm kind of busy these days, sorry. Does
someone else from net-mail volunteers to do that sooner?

Um, I forgot to mention it here - 4.64-r2 is in portage, with updated
chappa-all patch. Give it a try, please.

(In reply to comment #4)
> 4.64-r2 is in portage, with updated
> chappa-all patch. Give it a try, please.
> 
Sorry, same crash happens...
I'll also inform comp.mail.pine (and thus Eduardo Chappa).
Maybe it's not his patch that's the problem?

(In reply to comment #5)
> (In reply to comment #4)
> > 4.64-r2 is in portage, with updated
> > chappa-all patch. Give it a try, please.
> > 
> Sorry, same crash happens...
> I'll also inform comp.mail.pine (and thus Eduardo Chappa).
> 
Ok, Eduardo Chappa looked at it again, and after he helped me through my first
gdb session, he got the info needed to correct the problem.  The updated
patches are on his website.

I suggest incorporating the new patches and doing a version revision to
pine-4.64-r3.  This update is for all platforms.

Thanks for the attention,

Erik

Bumped in portage. Please test newly added 4.64-r3.

(In reply to comment #7)
> Bumped in portage. Please test newly added 4.64-r3.
> 
Tested. The problem has been resolved.

Good, I'm glad this issue is fixed. Closing bug, and thank you (and Eduardo)
for caring!