Bret Busby
2010-02-01 05:53:23 UTC
Hello.
I do not know whether this list still works, but, as this is a problem
relating to PINE, and not to ALPINE, I am posting this query to this
list.
I am using PINE 4.64; from what I understand, the last stable (or,
relatively stable) version of PINE.
Today, when I tried to run PINE, after it performing its archiving, it
collapsed, with the returned error;
"Problem detected: "Received abort signal(sig=11)".
Pine Exiting.
"
Of course, like much of available software, the error message is
meaningless to a simple user.
In trying to run it with debugging flags, I looked at the man entry for
PINE, and found
"-d debug-level Output diagnostic info at debug-level (0-9) to the
current .pine-debug[1-4] file. A value of
0 turns debugging off and suppresses the
.pine-debug file.
-d key[=val] Fine tuned output of diagnostic
messages where "flush" causes debug file writing without
buffering, "timestamp" appends each message
with a timestamp, "imap=n" where n is between 0
and 4 representing none to verbose IMAP
telemetry reporting, "numfiles=n" where n is between 0
and 31 corresponding to the number of debug
files to maintain, and "verbose=n" where n is
between 0 and 9 indicating an inverse
threshold for message output.
"
Without clearly uinderstanding that, and, without clearly understanding
the required syntax, I first tried running
pine -d
That did not work, so, I tried
pine -d verbose=5
and I got
" pine -d verbose=5
Argument Error: unknown flag "d", debugging not compiled in
"
What does the error that causes PINE to crash, mean, and, why did PINE
suddenly stop working without crashing, and, what needs to happen, to
get PINE working without crashing, again?
Please do not reply with "get rid of PINE and install ALPINE", as I am
familiar with PINE, and I do not know that ALPINE will work the same,
with the many folders and filters and other things implemented, and,
changing software can in itself, cause problems.
I have just subscribed to the list, using an alternative email address
that uses webmail and not PINE, and I will have to be using that email
address until I find the resolution of the problem.
Thank you in anticipation
--
Bret Busby
Armadale
West Australia
..............
"So once you do know what the question actually is,
you'll know what the answer means."
- Deep Thought,
Chapter 28 of Book 1 of
"The Hitchhiker's Guide to the Galaxy:
A Trilogy In Four Parts",
written by Douglas Adams,
published by Pan Books, 1992
....................................................
I do not know whether this list still works, but, as this is a problem
relating to PINE, and not to ALPINE, I am posting this query to this
list.
I am using PINE 4.64; from what I understand, the last stable (or,
relatively stable) version of PINE.
Today, when I tried to run PINE, after it performing its archiving, it
collapsed, with the returned error;
"Problem detected: "Received abort signal(sig=11)".
Pine Exiting.
"
Of course, like much of available software, the error message is
meaningless to a simple user.
In trying to run it with debugging flags, I looked at the man entry for
PINE, and found
"-d debug-level Output diagnostic info at debug-level (0-9) to the
current .pine-debug[1-4] file. A value of
0 turns debugging off and suppresses the
.pine-debug file.
-d key[=val] Fine tuned output of diagnostic
messages where "flush" causes debug file writing without
buffering, "timestamp" appends each message
with a timestamp, "imap=n" where n is between 0
and 4 representing none to verbose IMAP
telemetry reporting, "numfiles=n" where n is between 0
and 31 corresponding to the number of debug
files to maintain, and "verbose=n" where n is
between 0 and 9 indicating an inverse
threshold for message output.
"
Without clearly uinderstanding that, and, without clearly understanding
the required syntax, I first tried running
pine -d
That did not work, so, I tried
pine -d verbose=5
and I got
" pine -d verbose=5
Argument Error: unknown flag "d", debugging not compiled in
"
What does the error that causes PINE to crash, mean, and, why did PINE
suddenly stop working without crashing, and, what needs to happen, to
get PINE working without crashing, again?
Please do not reply with "get rid of PINE and install ALPINE", as I am
familiar with PINE, and I do not know that ALPINE will work the same,
with the many folders and filters and other things implemented, and,
changing software can in itself, cause problems.
I have just subscribed to the list, using an alternative email address
that uses webmail and not PINE, and I will have to be using that email
address until I find the resolution of the problem.
Thank you in anticipation
--
Bret Busby
Armadale
West Australia
..............
"So once you do know what the question actually is,
you'll know what the answer means."
- Deep Thought,
Chapter 28 of Book 1 of
"The Hitchhiker's Guide to the Galaxy:
A Trilogy In Four Parts",
written by Douglas Adams,
published by Pan Books, 1992
....................................................