From owner-freebsd-current  Sun May 12 15:20:51 2002
Delivered-To: freebsd-current@freebsd.org
Received: from kayak.xcllnt.net (209-128-86-226.bayarea.net [209.128.86.226])
	by hub.freebsd.org (Postfix) with ESMTP id D68BB37B405
	for <current@FreeBSD.ORG>; Sun, 12 May 2002 15:20:46 -0700 (PDT)
Received: from dhcp01.pn.xcllnt.net (dhcp01.pn.xcllnt.net [192.168.4.201])
	by kayak.xcllnt.net (8.11.6/8.11.4) with ESMTP id g4CMKdJ99095;
	Sun, 12 May 2002 15:20:39 -0700 (PDT)
	(envelope-from marcel@kayak.pn.xcllnt.net)
Received: from dhcp01.pn.xcllnt.net (localhost [127.0.0.1])
	by dhcp01.pn.xcllnt.net (8.12.3/8.12.3) with ESMTP id g4CMKnfF021165;
	Sun, 12 May 2002 15:20:49 -0700 (PDT)
	(envelope-from marcel@dhcp01.pn.xcllnt.net)
Received: (from marcel@localhost)
	by dhcp01.pn.xcllnt.net (8.12.3/8.12.3/Submit) id g4CMKnmu021164;
	Sun, 12 May 2002 15:20:49 -0700 (PDT)
Date: Sun, 12 May 2002 15:20:48 -0700
From: Marcel Moolenaar <marcel@xcllnt.net>
To: Poul-Henning Kamp <phk@critter.freebsd.dk>
Cc: current@FreeBSD.ORG
Subject: Re: Keywords: pre-GCC3 tcsh coredump free/malloc reentrancy signal
Message-ID: <20020512222048.GB21019@dhcp01.pn.xcllnt.net>
References: <20020512212236.GB20876@dhcp01.pn.xcllnt.net> <3858.1021238862@critter.freebsd.dk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3858.1021238862@critter.freebsd.dk>
User-Agent: Mutt/1.3.99i
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-current.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-current>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-current>
X-Loop: FreeBSD.ORG

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?

-- 
 Marcel Moolenaar	  USPA: A-39004		 marcel@xcllnt.net

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message