[Pine-4.63] buglet ???

[Chiefy]

I've noticed a problem.

M -> S -> K -> scroll down to 'HEADER COLORS' add one header then delete it.

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

If more than one header is present there's no error.

--
Q: How many IBM 370's does it take to execute a job?
A: Four, three to hold it down, and one to rip its head off.

[Eduardo Chappa]

*** Chiefy (el...@non.existent.invalidet) wrote in comp.mail.pine today:

:) I've noticed a problem.
:)
:) M -> S -> K -> scroll down to 'HEADER COLORS' add one header then
:) delete it.
:)
:) Problem detected: "Received abort signal(sig=11)".
:) Pine Exiting.

Right, the problem is that Pine goes too far trying to look for a line
where it could set the cursor, and so several things fail because of that.

I have a patch in my web page that fixes this problem.

--
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

[Chiefy]

25 Jul 2005 22:45 UTC, Eduardo Chappa typed:

> Right, the problem is that Pine goes too far trying to look for a line
> where it could set the cursor, and so several things fail because of that.
>
> I have a patch in my web page that fixes this problem.

Eduardo, many thanks again.
Glad to report your patch fixes the problem (slx build).

I'm wondering if this was the correct place to report a possible problem.
Do you know if the Pine team have an official bug reporting procedure, or
is this forum acceptable?

--
Hildebrant's Principle:

If you don't know where you are going, any road will get you there.

[Eduardo Chappa]

*** Chiefy (el...@non.existent.invalidet) wrote in comp.mail.pine today:

:) 25 Jul 2005 22:45 UTC, Eduardo Chappa typed:
:) > Right, the problem is that Pine goes too far trying to look for a
:) > line where it could set the cursor, and so several things fail
:) > because of that.
:) >
:) > I have a patch in my web page that fixes this problem.
:)
:) Eduardo, many thanks again.
:) Glad to report your patch fixes the problem (slx build).

Great!. I'm glat to read that :)

:) I'm wondering if this was the correct place to report a possible
:) problem. Do you know if the Pine team have an official bug reporting
:) procedure, or is this forum acceptable?

As of today, there is no "bugzill" for Pine. However, forums like these
are read by the developers of Pine, so they know about these things. In
case they forget I remind them during alpha testing.

You can also send your reports to pi...@cac.washington.edu, but unless it's
a security bug, I would advise you to either post it here or to the
pine-info list, so that it can be seen by others (like me), and maybe a
patch will come out of it, as it was in this case.

[Jeff Franklin]

On Tue, 26 Jul 2005, Eduardo Chappa wrote:

> :) Eduardo, many thanks again.
> :) Glad to report your patch fixes the problem (slx build).
>
> Great!. I'm glat to read that :)

We'll definitely add this patch to the pine sources. Thanks Eduardo!

> You can also send your reports to pi...@cac.washington.edu, but unless it's
> a security bug, I would advise you to either post it here or to the
> pine-info list, so that it can be seen by others (like me), and maybe a
> patch will come out of it, as it was in this case.

Eduardo is correct. What some people do and what I find helpful as
one of the developers is that they send an email to
pi...@cac.washington.edu and they post either to pine-info or
comp.mail.pine. Sending it to pine@cac puts it on our radar, and having
it out there on the forum helps us see if others are having similar
problems. Eduardo's input is always very useful too.

Jeff