From owner-freebsd-current Sun May 12 15:32:54 2002 Delivered-To: freebsd-current@freebsd.org Received: from relay.pair.com (relay1.pair.com [209.68.1.20]) by hub.freebsd.org (Postfix) with SMTP id 4163437B403 for ; Sun, 12 May 2002 15:32:52 -0700 (PDT) Received: (qmail 16012 invoked from network); 12 May 2002 22:32:51 -0000 Received: from 12-236-91-101.client.attbi.com (HELO ?10.1.1.198?) (12.236.91.101) by relay1.pair.com with SMTP; 12 May 2002 22:32:51 -0000 X-pair-Authenticated: 12.236.91.101 Mime-Version: 1.0 X-Sender: (Unverified) Message-Id: In-Reply-To: <20020512222048.GB21019@dhcp01.pn.xcllnt.net> References: <20020512212236.GB20876@dhcp01.pn.xcllnt.net> <3858.1021238862@critter.freebsd.dk> <20020512222048.GB21019@dhcp01.pn.xcllnt.net> Date: Sun, 12 May 2002 15:32:49 -0700 To: Marcel Moolenaar From: Mark Peek Subject: Re: Keywords: pre-GCC3 tcsh coredump free/malloc reentrancy signal Cc: current@FreeBSD.ORG, Poul-Henning Kamp Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 3:20 PM -0700 5/12/02, Marcel Moolenaar wrote: >On Sun, May 12, 2002 at 11:27:42PM +0200, Poul-Henning Kamp wrote: >> >> It is not legal to recursively call malloc/free/realloc, and therefore >> you should either protect all calls to malloc/free/realloc by blocking >> signals or better: not call them in signal handlers. > >Ok, thanks. I guess we have a genuine tcsh(1) bug here. > >Who's maintaining tcsh? Can he/she suggest what to do or otherwise >take it from here? I've been maintaining tcsh. Can you file a PR and assign it to me? I'll follow up with the tcsh owner to resolve the problem. Mark To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message