Problem detected: "Received abort signal(sig=11)". Pine Exiting. This problem started kinda out of the blue- initially I could not start pine at all, then i figured out the existence of the ~/.maildir/.uidvalidity file caused it to crap out on me and refuse to start, however if i rm'd that file it would start fine- until i quit, and then the file would need to be rm'd again. I upgraded to 4.61 and while it does not have this exact problem, it segfaults semi-randomly on start, while moving around the index list- it seems to crash every other time i hit 'q' or 'x', etc. Reproducible: Always Steps to Reproduce: 1. use pine ;] 2. 3. Actual Results: Problem detected: "Received abort signal(sig=11)". Pine Exiting. Not really sure what caused it, it was always kinda buggy, but all of a sudden a week or so ago it got a lot worse. Portage 2.0.51_rc6 (hardened/amd64, gcc-3.3.4, glibc-2.3.4.20040808-r0, 2.6.7-ha rdened-r7 x86_64) ================================================================= System uname: 2.6.7-hardened-r7 x86_64 Gentoo Base System version 1.5.3 Autoconf: sys-devel/autoconf-2.59-r4 Automake: sys-devel/automake-1.8.5-r1 Binutils: sys-devel/binutils-2.15.90.0.1.1-r3 Headers: sys-kernel/linux26-headers-2.6.6-r1 Libtools: sys-devel/libtool-1.5.2-r5 ACCEPT_KEYWORDS="amd64" AUTOCLEAN="yes" CFLAGS="-O2 -pipe" CHOST="x86_64-pc-linux-gnu" COMPILER="" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3/s hare/config /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache distlocks sandbox" GENTOO_MIRRORS="http://gentoo.osuosl.org/ ftp://ibiblio.org/pub/Linux/distributi ons/gentoo/ ftp://ftp.gtlib.cc.gatech.edu/pub/gentoo http://csociety-ftp.ecn.pur due.edu/pub/gentoo/ ftp://csociety-ftp.ecn.purdue.edu/pub/gentoo/ ftp://ftp.ussg .iu.edu/pub/linux/gentoo ftp://ftp.ucsb.edu/pub/mirrors/linux/gentoo/ http://gen too.seren.com/gentoo http://gentoo.chem.wisc.edu/gentoo/ ftp://gentoo.chem.wisc. edu/gentoo/ http://gentoo.mirrors.pair.com/ ftp://gentoo.mirrors.pair.com/ http: //gentoo.ccccom.com ftp://gentoo.ccccom.com http://ftp-mirror.internap.com/pub/g entoo/ ftp://ftp-mirror.internap.com/pub/gentoo/ http://mirrors.tds.net/gentoo f tp://mirrors.tds.net/gentoo http://gentoo.netnitco.net ftp://gentoo.netnitco.net /pub/mirrors/gentoo/source/ http://mirror.tucdemonic.org/gentoo/ http://mirror.c larkson.edu/pub/distributions/gentoo/ http://mirrors.acm.cs.rpi.edu/gentoo/ http ://lug.mtu.edu/gentoo/ ftp://lug.mtu.edu/gentoo/source ftp://ftp.ndlug.nd.edu/pu b/gentoo/ http://open-systems.ufl.edu/mirrors/gentoo http://gentoo.llarian.net/ ftp://gentoo.llarian.net/pub/gentoo http://gentoo.binarycompass.org http://mirro r.datapipe.net/gentoo http://mirror.datapipe.net/gentoo http://gentoo.eliteitmin ds.com http://www.gigaload.org/gentoo.org/ http://chod.cwru.edu/gentoo ftp://cho d.cwru.edu/gentoo http://gentoo.cs.lewisu.edu/gentoo/ ftp://linux.cs.lewisu.edu/ gentoo/" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X aalib acl acpi aim alsa amd64 bcmath berkdb bzlib calendar caps crypt csc ope dlloader doc esd fam fbcon gd gdbm gif gnome gnutls gphoto2 gpm gps gstreame r gtk gtk2 hardened icq imap imlib ipv6 jpeg libwww maildir mhash mime mmap moti f mozilla mpeg multilib mysql mysqli ncurses offensive oggvorbis opengl oscar pa m pcntl pcre perl pfa pic pie png posix prelude python qt quicktime readline sla ng spell ssl sysvipc tcltk tcpd tiff truetype unicode vhosts xinerama xml xml2 x mms xosd zlib"
> Portage 2.0.51_rc6 (hardened/amd64, gcc-3.3.4, glibc-2.3.4.20040808-r0, 2.6.7-hardened-r7 x86_64) hardened,AMD64 please help confirm/resolve this.
lv this is all you bud.
ok it doesnt seem so random: if i do pine -i , the first time it always crashes (unless there is no new mail) the second time, it goes through fine. If I have new mail and delete them, the first time I try to expunge them, it crashes- works fine the second time through. On a more random basis, hitting 'q' to quit causes the crash. About 1 in 5 emails I write cause the crash. I just did an strace- however because of the custom signal handler's its hard to determine whats what here- looks like it was going through /home/me/.maildir/cur on crash. I also updated to pine-4.61-r2 in hopes maybe something had been fixed.
Have the same problem so tried to merge a older version. 4.50-r4 seems ok (but no maildir for the inbox dir). When the problem should occurs I have the following message without the crash (signal 11) : "Warning: Folder has changed in an unexpected way. Reloading."
Could you guy try this patch instead and report back. It looks like the patch has changed. http://www.math.washington.edu/~chappa/pine/patches/pine4.61/all.patch.gz $ wget http://www.math.washington.edu/~chappa/pine/patches/pine4.61/all.patch.gz $ cp all.patch.gz /usr/portage/distfiles/pine-4.61-r1-chappa-all.patch.gz $ ebuild /usr/portage/mail-client/pine-4.61-r2.ebuild digest $ sudo emerge pine If it fixes the problem, we'll commit it soon.
Ok, applied the new patch and everything- one small detail- the ebuild is actually in /usr/portage/mail-client/pine/pine-... not a big deal at all however. So far (the last ten minutes or so it hasnt crashed.) it seems fairly stable- lemme try it out for a few days and I will let you know.
hm, I applied the patch and no more crash but... no more mails. I mean when I go in a maildir in a shell, I see 380 mails but if I open it with pine, only 45 are shown. Will try to figure out why.
I had the same problem- in my use string I believe I have "maildir mbox", what was happening to me was that all my mails were ending up in mbox format for some reason? I also noticed that ~/.maildir/cur and ~/.maildir/new suddenly turned into a directory? Thus pine was not seeing them. I first just made a new folder and cat'd all my email into that folder and that worked, then after using mailx to check my mail a few times- when i started pine it decided to convert my email from mbox format to maildir, no idea why it decided to do it that time. However yes, it stopped crashing ;]
hm don't have mbox in my USE string. The mail shown in pine are in the 1090498261.4194.ZcGy1:2,S filename format. The others are in msg.8Th:2,S filename format. Sorry but I don't know too much of mailbox and maildir format (except that mbox is 1 huge file and mdir each msg are one file). I use fetchmail and procmail to retrieve and put messages in dir. Maybe I should look at them.
oh. actually, excuse me- i just checked make.conf and i no longer have mbox support (I think I changed it to -mbox when I first started having problems with pine). I also use procmail, I think it may be related to that ? It's a shot in the dark honestly, but I have procmail setup to log and I noticed my mta was transporting the mail correctly and handing it off to procmail who was sticking it as individual files in each target directory. This also happened when I first setup procmail and I had made the mistake of trying to create my folders manually. At the moment, I've disabled procmail until I get some tiem to look into it (Believe it or not I program for a living, I just don't have the time to spend tracking bugs in other peoples software, I have enough of my own to deal with). Also, the msg files seem to be the plain-text copy of the email, while the others appear to be the html version of them? Or at least thats what I saw on my box. I think sometime tonight I might try mv'ing the maildir and then sending myself emails that would go into each folder and see if I can get procmail to work out its own problems- however I am still not sure exactly what I did to get the process working again- I just happened to notice one time when I started up that it said something to the effect of 'converting email from mbox format'
It's not amd64 problem, remove them from CC. maildir and mbox USE flags have been removed as you don't need them anymore. Quoted fom the postinst: * This build of Pine has Maildir support built in as * part of the chappa-all patch. * * If you have a maildir at ~/Maildir it will be your * default INBOX. The path may be changed with the * "maildir-location" setting in Pine. * * If you don't have any maildirs Pine works as before * with the INBOX at /var/spool/mail/. * You may want to take a look at ~/.pinerc or mv it to somewhere and restart pine to have it recreate and compare them. I myself don't use pine. I just emerge it to test and it works out of the box. All I only have to edit .pinerc maildir-location=".maildir" line. My MTA is postfix.
hrm this actually appears to be that pine does in fact have mbox support even though it has the -mbox, although I understand it doesnt make use of them anymore. The problem is not in my pinerc, I've been using pine for years without incident and am fairly familar with the syntax- I did check it to make sure it hadn't changed and it has not. For whatever reason, pine is choosing to read ~/mbox as opposed to ~/.maildir/new
New pine 4.62 requires you to choose between mbox and maildir exclusive usage, could you please give it a whirl?
Date: Thu, 3 Feb 2005 12:51:44 -0800 (PST) From: Eduardo Chappa <chappa@math.washington.edu> To: Pine Discussion Forum <pine-info@u.washington.edu> Subject: Re: PINE 4.61, 4.62 segmentation fault... *** Alex V. Koval (antalex@halogen-dg.common) wrote in the pine-info list today: :) On some spam email message pine sigfaults. I think it is a bad sign if :) someone could sigfault email program via specially crafted email :) message. Thanks Alex, The bug is in a patch of mine which does advanced justification. I have fixed the bug and corrected patches can be downloaded from my web page. Thank you! -- Eduardo Patches/Help: http://www.math.washington.edu/~chappa/pine/ XML/RSS feed: http://www.math.washington.edu/~chappa/pine/pine.xml
Looks like this bug has reappeared in >=pine-4.62.
Could you be a little more specific? Which revision of 4.62 are you using? Also, could you please attach a sample email which makes pine crash like this?
Created attachment 56964 [details] sample message that causes >=pine-4.62 to sig=11
Hi Andrej, I get a sig=11 for versions 4.62, 4.62-r1 and 4.62-r2. pine-4.61-r5 seems to work fine.
I'm afraid that message sample is unusable, unless pine understands rtf by some chance - I was asking for a complete (with headers) mbox-formatted email to be opened in pine.
Could you try new pine 4.63 to see if this is fixed?.
Feel free to reopen with requested info.
