My PC-Pine 4.64 does not crash.
I think it does not like the comma separated full name, am I right?
Regards,
Mario
Pine should handle that without difficulty.
-- Mark --
http://panda.com/mrc
Democracy is two wolves and a sheep deciding what to eat for lunch.
Liberty is a well-armed sheep contesting the vote.
Can you reproduce this crash, and provide us with a reliable script of
things to do to make the crash happen?
Do you have a core dump from this crash? Do you know how to do a stack
trace from the core dump?
If this is a bug in the UW distributed version, we would like to fix it.
-- Mark --
> On Fri, 27 Jan 2006, Mario F. Duhanic wrote:
>> I think it does not like the comma separated full name, am I right?
>
> Pine should handle that without difficulty.
Strange, I have just tried to play around with PC-Pine
and the originally mentioned address and PC-Pine 4.64 crashed.
Reproduction:
I took the original article and told pine to forward it,
then I inserted the mentioned (test) address (Lastname,Firstname)
via paste into the to-field.
Then I appended a ";" (because Pine did not like to have a comma
there) and pasted the same address again.
After that I changed the ";" into a ",".
That's the ending of the resulting pinedbg-file (no extra debug level):
| ---- COMPOSER ----
|IMAP 22:44:27 1/27 mm_log parse: Unexpected characters at end of address:
|;"Lastname, First" <F.Las...@mbox.econ.some-university.de>
|build_address_internal returning parse error: Unexpected characters at end
|of address: ;"Lastname, First" <F.Las...@mbox.econ.some-university.de>
|IMAP 22:44:31 1/27 mm_log parse: Unexpected characters at end of address:
|;"Lastname, First" <F.Las...@mbox.econ.some-university.de>
|build_address_internal returning parse error: Unexpected characters at end
|of address: ;"Lastname, First" <F.Las...@mbox.econ.some-university.de>
|IMAP 22:44:44 1/27 mm_log parse: Unterminated mailbox:
|F.Las...@mbox.econ.
|IMAP 22:44:44 1/27 mm_log parse: Unexpected characters at end of address:
|>
|build_address_internal retur
Regards,
Mario
> Can you reproduce this crash, and provide us with a reliable script of things
> to do to make the crash happen?
just tried and it crashed again upon second attempt. Then tried again and
what I do is ctrl-u the second address right after the first which gives
no comma between the two, breaks the second across lines putting a comma
at the end of the first line and a comma at the end of the second. Then
remove the comma at the end of the second line, move forward/back the
cursor and it goes
> Do you have a core dump from this crash? Do you know how to do a stack trace
> from the core dump?
if you explain to me how to find/do this then I'll do it
> If this is a bug in the UW distributed version, we would like to fix it.
yes, used to compile it myself but this is from some possibly unofficial
debian package.
Gerald
:) On Fri, 27 Jan 2006, Mark Crispin wrote:
:)
:) > Can you reproduce this crash, and provide us with a reliable script
:) > of things to do to make the crash happen?
:)
:) just tried and it crashed again upon second attempt. Then tried again
:) and what I do is ctrl-u the second address right after the first which
:) gives no comma between the two, breaks the second across lines putting
:) a comma at the end of the first line and a comma at the end of the
:) second. Then remove the comma at the end of the second line, move
:) forward/back the cursor and it goes
Gerald,
I have a patch that fixes this in my web page. See below.
--
Eduardo
Patches/Help: http://www.math.washington.edu/~chappa/pine/
XML/RSS feed: http://www.math.washington.edu/~chappa/pine/pine.xml
Please send spam to webmaster@localhost
> Gerald,
>
> I have a patch that fixes this in my web page. See below.
many thanks - what a great service. Guess I can simply wait for 4.65 to
get the patch - and some of the others which seem useful as well.
thanks again, Gerald
:) On Fri, 27 Jan 2006, Eduardo Chappa wrote:
:)
:) > Gerald,
:) >
:) > I have a patch that fixes this in my web page. See below.
:)
:) many thanks - what a great service. Guess I can simply wait for 4.65 to
:) get the patch - and some of the others which seem useful as well.
Gerald,
Thank you for your nice comments!
I am sure this patch (or equivalent) will be in version 4.65. If you
want any of the new features in my patches you will have to patch them
yourself, for any version you consider using.