Steve Ames writes:
> > We *do* know who that is. This however is a more tcsh-specific issue,
> > and raising it with the tcsh author would probably lead you to faster
> > happiness. Is there some reason you wont email him about this?
>
> Except it isn't tcsh specific really.
>
> Our config.h 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? 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*
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:
<12:10pm>thunder/gallatin:/tmp>uname -sr
FreeBSD 4.4-RC
<12:10pm>thunder/gallatin:/tmp>setenv MALLOC_OPTIONS 'AJ'
<12:10pm>thunder/gallatin:/tmp>tcsh
tcsh 6.10.00 (Astron) 2000-11-19 (alpha-digital-FreeBSD) options
8b,nls,dl,al,kan,sm,rh,color,dspm
<12:10pm>thunder/gallatin:/tmp>set rmstar
<12:10pm>thunder/gallatin:/tmp>rm *
Do you really want to delete all files? [n/y] n
Segmentation fault (core dumped)
Note that -current has malloc options 'AJ' on by default to catch just
this kind of bug.
Drew
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
