From owner-freebsd-current Sun May 12 14:32:58 2002 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 3ADD337B403 for ; Sun, 12 May 2002 14:32:56 -0700 (PDT) Received: from khavrinen.lcs.mit.edu (localhost [IPv6:::1]) by khavrinen.lcs.mit.edu (8.12.3/8.12.3) with ESMTP id g4CLWmEN017652; Sun, 12 May 2002 17:32:49 -0400 (EDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.12.3/8.12.3/Submit) id g4CLWmHl017649; Sun, 12 May 2002 17:32:48 -0400 (EDT) Date: Sun, 12 May 2002 17:32:48 -0400 (EDT) From: Garrett Wollman Message-Id: <200205122132.g4CLWmHl017649@khavrinen.lcs.mit.edu> To: Poul-Henning Kamp Cc: Marcel Moolenaar , current@FreeBSD.ORG Subject: Re: Keywords: pre-GCC3 tcsh coredump free/malloc reentrancy signal In-Reply-To: <3858.1021238862@critter.freebsd.dk> References: <20020512212236.GB20876@dhcp01.pn.xcllnt.net> <3858.1021238862@critter.freebsd.dk> 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 < said: > The correct solution is probably to set a flag in the signal handler > and resize the buffer before the next line is read. Or, somewhat less optimally, to block SIGWINCH (and any other signals with similar handler behavior) around calls to malloc and free. This is still not *correct*, mind you, but will make the condition less likely. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message