Subject: Email that crashes pine 4.60

From: Christopher Fisk <[email-masked]>
Date: Thu, 11 Nov 2004 12:04:48 -0500 (EST)

I've recently received a spam email message that crashes pine when I 
choose to view headers on the message.  Where is the best place to report 
this?

http://chris.uasoft.com/pine/pinecrash.bz2

Thanks,

Christopher Fisk
-- 
BOFH Excuse #231:
We had to turn off that service to comply with the CDA Bill.
-- 
-----------------------------------------------------------------
 For information about this mailing list, and its archives, see: 
 http://www.washington.edu/pine/pine-info/
-----------------------------------------------------------------

---

From: Eduardo Chappa <[email-masked]>
Date: Thu, 11 Nov 2004 09:30:19 -0800 (PST)

*** Christopher Fisk ([email-masked]) wrote today:

:) I've recently received a spam email message that crashes pine when I 
:) choose to view headers on the message. 

Your test message does not crash my copy of Pine, either 4.60 or 4.61. It 
is probably due to some configuration that you have enabled that I have 
not. Would you care to share your .pinerc too? (remove names of servers, 
and anything you consider private). I am more interested in what is under 
feature-list, colors, etc.

-- 
Eduardo
Patches/Help: http://www.math.washington.edu/~chappa/pine/
XML/RSS feed: http://www.math.washington.edu/~chappa/pine/pine.xml

---

From: Christopher Fisk <[email-masked]>
Date: Thu, 11 Nov 2004 13:03:57 -0500 (EST)

> feature-list, colors, etc.

http://chris.uasoft.com/pine/.pinerc

borg chrisf/mail# ldd /usr/bin/pine
         linux-gate.so.1 =>  (0xffffe000)
         libncurses.so.5 => /lib/libncurses.so.5 (0x40030000)
         libpam.so.0 => /lib/libpam.so.0 (0x40075000)
         libdl.so.2 => /lib/libdl.so.2 (0x4007d000)
         libssl.so.0.9.7 => /usr/lib/libssl.so.0.9.7 (0x40080000)
         libcrypto.so.0.9.7 => /usr/lib/libcrypto.so.0.9.7 (0x400b1000)
         libc.so.6 => /lib/libc.so.6 (0x401ac000)
         /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)

When i view the message, it views fine,  when I hit "h" to view all 
headers I get:

Problem detected: "Received abort signal(sig=11)".
Pine Exiting.

1:02pm (chrisf@borg) /home/chrisf (26) pine -v
Pine 4.60 built Wed Sep 8 21:34:28 EDT 2004 on borg.mhonline.net

I've been using pine on linux since 1996, so you can assume my linux and 
pine skills are above average =)

Christopher Fisk
-- 
Is it a right to remain ignorant?
 	-- Calvin

---

From: NM Public <[email-masked]>
Date: Thu, 11 Nov 2004 18:15:24 +0000 (GMT)

I recently discovered a crashing Pine bug (which I will report 
soon), which is fixed by *not* specifying viewer-hdrs, i.e., 
having this in your pinerc:

viewer-hdrs=

This probably won't fix your crash, but it's worth a try!

Hope it helps,
NM

-- 
Infinite Ink: <http://www.ii.com/>
All About Pine: <http://www.ii.com/internet/messaging/pine/>
Power Pine: <http://www.ii.com/internet/messaging/pine/pc/>

---

From: Christopher Fisk <[email-masked]>
Date: Thu, 11 Nov 2004 13:23:22 -0500 (EST)

On Thu, 11 Nov 2004, NM Public wrote:

> I recently discovered a crashing Pine bug (which I will report soon), which is 
> fixed by *not* specifying viewer-hdrs, i.e., having this in your pinerc:
>
> viewer-hdrs=
>

Well, my crash is only happening with that one message, not any other 
ones.  My thoughts were that it's triggering something in pine that normal 
messages don't.  I figured that 1 message out of literally thousands I've 
received that crashes pine is probably a rarely hit bug that is being 
triggered.  Then again, I'm not a programmer, just a user.

Christopher Fisk
-- 
If there was any justice, my face would be on a bunch of crappy merchandise!
 	-- Homer Simpson, Flaming Moe's

---

From: Eduardo Chappa <[email-masked]>
Date: Thu, 11 Nov 2004 10:26:25 -0800 (PST)

*** Christopher Fisk ([email-masked]) wrote in the pine-info list...:

:) > Your test message does not crash my copy of Pine, either 4.60 or 
:) > 4.61. It is probably due to some configuration that you have enabled 
:) > that I have not. Would you care to share your .pinerc too? (remove 
:) > names of servers, and anything you consider private). I am more 
:) > interested in what is under feature-list, colors, etc.
:) 
:) http://chris.uasoft.com/pine/.pinerc

Thank you Christopher. Still no luck. Too bad. This means a couple of 
things:

  * Either your version of Pine has been modified in some ways which mine 
    has not, so I can not reproduce the crash, or

  * There's a missing piece in your report.

If it's the first one, I would suggest that you try to build your own 
version of Pine *4.61* without any modifications and see if you can 
reproduce the crash, if so, then you should run Pine under gdb and report 
back the results of this investigation.

If it's the second case, try to think as to what could make a difference. 
E.g. you are accessing the folder through a server, or other condition 
that you think may affect the result.

It's been the case before that I've not been able to reproduce bugs 
reported by other people, so don't despair, maybe there's someone out 
there who can figure out what's going on.

---

From: Christopher Fisk <[email-masked]>
Date: Thu, 11 Nov 2004 13:43:02 -0500 (EST)

> there who can figure out what's going on.

FWIW, I'm using the latest unmasked ebuild from gentoo to build this pine. 
I'm unmasking the 4.61 ebuild now and will upgrade.

the ebuild this version of pine was build under is located at: 
http://chris.uasoft.com/pine/pine-4.60.ebuild, so you should be able to 
see if any special patches were used.

I'm using Gentoo:

CFLAGS="-mcpu=athlon-xp -O3 -pipe"

That said,  just finished my 4.61 emerge and the message no longer crashes 
pine.

Probably just a fluke.

Christopher Fisk
-- 
BOFH Excuse #393:
Interference from the Van Allen Belt.