bin/92074: [patch] top(1) aborts in redzone

[Steven G. Kargl]

Remko Lodder wrote:
[ Charset ISO-8859-1 unsupported, converting... ]
> Steven G. Kargl wrote:
> > edwin at FreeBSD.org wrote:
> >> Synopsis: [patch] top(1) aborts in redzone
> >>
> >> State-Changed-From-To: open->feedback
> >> State-Changed-By: edwin
> >> State-Changed-When: Thu Sep 25 15:53:39 UTC 2008
> >> State-Changed-Why: 
> >>> The above happened as I was resizing an xterm with an
> >>> actively run top(1).  This is on amd64 with malloc.c
> >>> v 1.100.
> >> Resizeing from which size to which size? I had it here in an xterm
> >> of 1x3 and 1200x400 and it kept working.
> >>
> >> I would like to see if this is resolved with the upgrade to 3.8b1
> >> so I need to know how to reproduce it.
> >>
> > 
> > It's unclear to me if you're asking me specifically about the PR
> > or one of the other individuals who have responded to the PR.
> > 
> > In any case, the answer to your question is "I don't know, 
> > and I don't care."
> > 
> 
> If you do not care, why should we do our best to help you?
> You submitted a bug ticket with a problem mentioning that your
> top(1) blew up while resizing it in xterm. Edwin tries to resolve
> that problem, so he asks you some specifics to get that going.
> 
> Now you tell us that you do not know and dont care. If that is
> really true, then please do not submit any problem reports at
> all. We as a community try to invest time in resolving problems
> that get in, if then submitters just "interestingly" say that
> they do not care, why should we invest the time?

Don't worry. I stopped submitting PRs a few years ago because
previous submissions were seldomly addressed in a timely manner
(see for example PR 92074).  I've chosen to limit my contributions
to fixing libm, and with libm I contact bde and das and standards
directly without touching send-pr.

With this particular PR, it was submitted on 20 Jan 06, which is,
oh, about 2.5 years ago.  The OS at that time was FreeBSD 7.0-CURRENT
#0: Thu Jan 19 13:50:25 PST 2006, and I have no idea what version of
Xorg and xterm I had.  I'm now running FreeBSD 8.0-CURRENT #2: Thu
Sep 4 09:47:25 PDT 2008.  The underlying malloc implementations are
different for the two versions of FreeBSD.  So, I can't test whether
the problem is fixed.

Edwin states he doesn't see the problem.  Was he running with
redzone(9) enable?  I don't know.  In fact, I can't remember and
have no way to determine if I was using redzone(9) on 20 Jan 06.
Edwin doesn't mention which version of FreeBSD he tested.

The audit trail of the PR shows two patches from two other
individuals (one is a FreeBSD committer!).  There is no
indication if either patch or both were committed.  Well,
a quick look at the repository with cvsweb suggest that 
that patches have not been applied.

Finally, I'll note that asked that the PR be closed a long time
ago.  Edwin re-opened the PR.  At that time, he should have
removed my contact information.

-- 
Steve
http://troutmask.apl.washington.edu/~kargl/