From: "David O'Brien" <[EMAIL PROTECTED]>
> > Now you could argue that perhaps the definition of SYSMALLOC just
exposes
> > a bug in tcsh?
>
> Maybe. One that cares should email Christos to find out if it is a bug
> or feature. Those that experience the problem are the ones in the best
> position to explain and get to the bottom of the issue.
>
> > OTOH, since the system version in -STABLE also defines SYSMALLOC and
> > still manages to work... you could also argue that this points to some
> > other bug in -CURRENT... lastly it could be argued that I'm barking up
> > completely the wrong tree. *shrug*
>
> Current and RELENG_4 do differ in the default malloc.conf settings.
> Current uses "ADJ<". Can you try those settings on RELENG_4 and see if
> it changes anything?
Andrew Gallatin pointed out that same thing. It seems the 'J' option is what
is causing the crash. That (I think?) makes this a tcsh bug. I'll submit a
problem
report to Christos (anyone have his address? Not readily findable at
www.tcsh.org).
In the interim (before he has a chance to look over the problem and offer a
correction)
would it be possible to stop defining SYSMALLOC? I'll submit a PR for it if
you
believe thats appropriate.
-Steve
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
