Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!helios!bcm!dimacs.rutgers.edu!seismo!uunet!mcsun!hp4nl!ruuinf!piet
From: piet@cs.ruu.nl (Piet van Oostrum)
Newsgroups: comp.lang.perl
Subject: Re: Problems with signal handler
Message-ID: <4767@ruuinf.cs.ruu.nl>
Date: 31 Jan 91 15:15:56 GMT
References: <1991Jan22.151906.9695@daimi.aau.dk> <1991Jan22.230448.28521@NCoast.ORG>
Sender: news@ruuinf.cs.ruu.nl
Reply-To: piet@cs.ruu.nl (Piet van Oostrum)
Organization: Dept of Computer Science, Utrecht University, The Netherlands
Lines: 14
In-reply-to: allbery@NCoast.ORG (Brandon S. Allbery KB8JRR)

>>>>> In message <1991Jan22.230448.28521@NCoast.ORG>, allbery@NCoast.ORG (Brandon S. Allbery KB8JRR) (BSA) writes:

BSA> There's no real fix for this, I suspect.  Anything that does I/O or uses
BSA> malloc() (including many list operations) can fail catastrophically (read:
BSA> core dump) in a signal handler.

The GNU malloc() is reentrant. I have read the code and I have reason to
believe that free() may give rise to problems, but that might have been
solved in the current release.
-- 
Piet* van Oostrum, Dept of Computer Science, Utrecht University,
Padualaan 14, P.O. Box 80.089, 3508 TB Utrecht, The Netherlands.
Telephone: +31 30 531806   Uucp:   uunet!mcsun!ruuinf!piet
Telefax:   +31 30 513791   Internet:  piet@cs.ruu.nl   (*`Pete')