Moving Mail into the INBOX

Paul Bartlett

unread,

Mar 12, 2007, 7:08:05 PM3/12/07

to

I use Pine 4.64 (what my ISP provides) on a netBSD system. I dial into
a server and use a telnet/SSH client to login to the shell account.
Because I get a lot of mailing list mail, I use procmail to sort much
of it out into various folders, which are actually files in a specified
directory in my file space. However, for a test (and for a reason) I
tried to move an email from one of those folders into my system INBOX.
With Pine open to the folder index, but without having tried to open
the item itself, I tried S(ave) to INBOX. All that did was cause Pine
to barf:

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

and I am back at the shell prompt. Is there a way to accomplish this?
(If I am not providing enough information, please ask.)

--
Paul Bartlett

Mark Crispin

unread,

Mar 12, 2007, 8:05:53 PM3/12/07

to

On Mon, 12 Mar 2007, Paul Bartlett wrote:
> I tried S(ave) to INBOX. All that did was cause Pine
> to barf:
> Problem detected: "Received abort signal(sig=?)".
> Pine Exiting
> Abort

That's a bug. If you can reproduce it, ask your ISP's technical support
to show you how to get a "stack trace" of the crash, and send that
information to the Pine team at UW: pi...@cac.washington.edu.

-- Mark --

http://staff.washington.edu/mrc
Science does not emerge from voting, party politics, or public debate.
Si vis pacem, para bellum.

Paul Bartlett

unread,

Mar 13, 2007, 5:37:24 PM3/13/07

to

On Mon, 12 Mar 2007, Mark Crispin wrote:

> On Mon, 12 Mar 2007, Paul Bartlett wrote:
>> I tried S(ave) to INBOX. All that did was cause Pine
>> to barf:
>> Problem detected: "Received abort signal(sig=?)".
>> Pine Exiting
>> Abort
>
> That's a bug. If you can reproduce it, ask your ISP's technical support to
> show you how to get a "stack trace" of the crash, and send that information
> to the Pine team at UW: pi...@cac.washington.edu.

My shell is tcsh. In my .cshrc I have 'pine' aliased to 'pine -d 0' so
as to suppress a debug file in normal operation. I can reproduce this
crash at will. I just did it by starting Pine as 'pine -d 4', which
resulted in a net command of 'pine -d 0 -d 4'. When I try the failing
command, I get a $HOME/.pine-crash file 66K (1306 lines) long with
minute detail. Will that be sufficient? If not, I can try to get a
stack trace. Or, it may be, that what I want to do is not doable. :-)

--
Paul Bartlett

Mark Crispin

unread,

Mar 13, 2007, 6:46:16 PM3/13/07

to

The .pine-crash file would be good to have, but so is the stack trace
(just run Pine under gdb, and then when it crashes do "info stack").
Thanks!

Paul Bartlett

unread,

Mar 13, 2007, 7:27:03 PM3/13/07

to

On Tue, 13 Mar 2007, Mark Crispin wrote:

> The .pine-crash file would be good to have, but so is the stack trace (just
> run Pine under gdb, and then when it crashes do "info stack"). Thanks!

OK, I got a stack trace. It was only eleven entries, though. I had to
run Pine again outside of gdb to get a crash file. I will forward them
both to the Pine team.

--
Paul Bartlett