From owner-freebsd-hackers  Fri Sep 19 04:37:19 1997
Return-Path: <owner-freebsd-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id EAA05617
          for hackers-outgoing; Fri, 19 Sep 1997 04:37:19 -0700 (PDT)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id EAA05612;
          Fri, 19 Sep 1997 04:37:15 -0700 (PDT)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id VAA14034; Fri, 19 Sep 1997 21:33:53 +1000
Date: Fri, 19 Sep 1997 21:33:53 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199709191133.VAA14034@godzilla.zeta.org.au>
To: bde@zeta.org.au, phk@critter.freebsd.dk
Subject: Re: Bug in malloc/free
Cc: atrens@nortel.ca, freebsd-bugs@FreeBSD.ORG, gram@cdsec.com,
        hackers@FreeBSD.ORG, julian@whistle.com, mike@smith.net.au
Sender: owner-freebsd-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>>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 :-).

Bruce