From owner-freebsd-hackers Tue Aug 28 10: 4:27 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from dragon.nuxi.com (dsl092-013-169.sfo1.dsl.speakeasy.net [66.92.13.169]) by hub.freebsd.org (Postfix) with ESMTP id 7C4D237B401 for ; Tue, 28 Aug 2001 10:04:21 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.5/8.11.1) id f7SH2rt97829; Tue, 28 Aug 2001 10:02:53 -0700 (PDT) (envelope-from obrien) Date: Tue, 28 Aug 2001 10:02:51 -0700 From: "David O'Brien" To: Steve Ames Cc: Jim Bryant , Charlie & , FreeBSD-hackers@FreeBSD.ORG Subject: Re: TCSH bug... Message-ID: <20010828100251.A97741@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <3B8AC157.5000203@yahoo.com> <020701c12f43$8e0e2310$28d90c42@eservoffice.com> <3B8AC8DB.5090603@yahoo.com> <004801c12f49$66cccb20$28d90c42@eservoffice.com> <20010827201407.A32152@virtual-voodoo.com> <3B8B05AF.9070004@yahoo.com> <20010827200243.A8113@dragon.nuxi.com> <20010828092016.B21396@virtual-voodoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010828092016.B21396@virtual-voodoo.com>; from steve@virtual-voodoo.com on Tue, Aug 28, 2001 at 09:20:16AM -0500 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, Aug 28, 2001 at 09:20:16AM -0500, Steve Ames wrote: > 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. 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 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? -- -- David (obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message