On Tue, Aug 28, 2001 at 08:36:28PM -0700, Kris Kennaway wrote:
Export a copy of the current tcsh code from contrib/tcsh, apply the
patch, and vendor import the entire thing with an appropriate tag (tag
style varies by contributed package, but I usually use something like
On Mon, Aug 27, 2001 at 09:45:03PM -0500, Jim Bryant wrote:
Someone recently commented in the tcsh/csh thread concerning the fact
that the FreeBSD tcsh is maintained separately from the port,
and nobody is really sure who is responsible for keeping the FreeBSD
version both in sync, AND,
and recompile then the TCSH bug goes away.
Now you could argue that perhaps the definition of SYSMALLOC just exposes
a bug in tcsh? 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
in /usr/src/bin/csh defines SYSMALLOC. The port does not.
The port works, the system version doesn't. If you comment out SYSMALLOC
in /usr/src/bin/csh/config.h and recompile then the TCSH bug goes away.
Now you could argue that perhaps the definition of SYSMALLOC just exposes
a bug in tcsh
On Tue, Aug 28, 2001 at 12:16:02PM -0400, Andrew Gallatin wrote:
Actually, it is a tcsh bug. Try playing with the MALLOC_OPTIONS
env. variable in -stable. Specifically, set it to 'AJ' I bet it will
drop core in -stable.
You would win that bet.
% uname -sr
FreeBSD 4.4-PRERELEASE
% export
then the TCSH bug goes away.
Then please submit a patch in a PR. I did the original config.h and I am
not a powerful CSH user, so I made best guesses. FreeBSD survives
because others get involved.
Now you could argue that perhaps the definition of SYSMALLOC just exposes
a bug in tcsh?
Maybe. One
From: Andrew Gallatin [EMAIL PROTECTED]
Actually, it is a tcsh bug. Try playing with the MALLOC_OPTIONS
env. variable in -stable. Specifically, set it to 'AJ' I bet it will
drop core in -stable. Eg:
[EXAMPLE DELETED]
Note that -current has malloc options 'AJ' on by default to catch just
At 12:19 PM -0500 8/28/01, Steven Ames wrote:
I will submit a problem report to Christos but I want to make sure
that I can explain exactly what is happening and why...
Memory is getting freed out from under a pointer to that memory. I just
submitted this patch to the tcsh mailing list and
On Tue, Aug 28, 2001 at 12:21:34PM -0500, Steven Ames wrote:
That (I think?) makes this a tcsh bug. I'll submit a problem report to
Christos
Much appreciated.
(anyone have his address? Not readily findable at www.tcsh.org).
$ grep @ /usr/src/contrib/tcsh/*
/usr/src/contrib/tcsh
On Tue, Aug 28, 2001 at 12:21:34PM -0500, Steven Ames wrote:
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?
Could you build tcsh from /usr/src with -g (and make sure not to strip
the binary when you
From: David O'Brien [EMAIL PROTECTED]
I'll submit a PR for it if you believe thats appropriate.
I am afraid, this would just cause people to forget about the problem
rather than to continue pursuing the problem.
Looks like Mark Peek found the problem and already submitted the
solution to
In message [EMAIL PROTECTED] Andrew Gallatin writes:
: Actually, it is a tcsh bug. Try playing with the MALLOC_OPTIONS
: env. variable in -stable. Specifically, set it to 'AJ' I bet it will
: drop core in -stable. Eg:
Dumps core for me too :-) Definely a tcsh bug.
Warner
To Unsubscribe
At 12:41 PM -0500 8/28/01, Steven Ames wrote:
From: David O'Brien [EMAIL PROTECTED]
I'll submit a PR for it if you believe thats appropriate.
I am afraid, this would just cause people to forget about the problem
rather than to continue pursuing the problem.
Looks like Mark Peek found the
-CURRENT from about 2 hours
ago.
-Steve
- Original Message -
From: Jim Bryant [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, August 27, 2001 4:53 PM
Subject: TCSH bug...
Sorry if this doesn't go here... I don't know where else to put it...
Please forward it to the correct
14 matches
Mail list logo
