From owner-freebsd-bugs  Fri Sep 19 05:51:23 1997
Return-Path: <owner-freebsd-bugs>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id FAA09571
          for bugs-outgoing; Fri, 19 Sep 1997 05:51:23 -0700 (PDT)
Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.26])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id FAA09546;
          Fri, 19 Sep 1997 05:51:13 -0700 (PDT)
Received: from critter.freebsd.dk (localhost.cybercity.dk [127.0.0.1])
	by critter.freebsd.dk (8.8.7/8.8.7) with ESMTP id OAA13894;
	Fri, 19 Sep 1997 14:50:07 +0200 (CEST)
To: Bruce Evans <bde@zeta.org.au>
cc: atrens@nortel.ca, freebsd-bugs@freebsd.org, gram@cdsec.com,
        hackers@freebsd.org, julian@whistle.com, mike@smith.net.au
Subject: Re: Bug in malloc/free 
In-reply-to: Your message of "Fri, 19 Sep 1997 21:33:53 +1000."
             <199709191133.VAA14034@godzilla.zeta.org.au> 
Date: Fri, 19 Sep 1997 14:50:07 +0200
Message-ID: <13892.874673407@critter.freebsd.dk>
From: Poul-Henning Kamp <phk@critter.freebsd.dk>
Sender: owner-freebsd-bugs@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

In message <199709191133.VAA14034@godzilla.zeta.org.au>, Bruce Evans writes:
>>>Flushing in abort() should be safe because abort() is not among the
>>>functions that are safe to call from a signal handler :-).
>>
>>Bummer.
>>
>>So what should I do in malloc when I realize that continuing doesn't
>>make sense ?
>>
>>	kill (diesig, getpid()); ?
>>	for which value of diesig ?
>
>Calling abort() from malloc() should be safe because malloc() is not
>among the functions that are safe to call from a signal handler :-).

I still seems to me that we need a new function to mean:
	"coredump, right now, no ifs, whens or buts. Thank you."

--
Poul-Henning Kamp             FreeBSD coreteam member
phk@FreeBSD.ORG               "Real hackers run -current on their laptop."