Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!crdgw1!uunet!dialogic!drich
From: drich@dialogic.com (Dan Rich)
Newsgroups: comp.unix.sysv386
Subject: malloc() problem solved(?)
Message-ID: <1991Apr09.215120.1734@dialogic.com>
Date: 9 Apr 91 21:51:20 GMT
Organization: Dialogic Corporation
Lines: 18

It looks like we may have a solution to our malloc() problems.  We
managed to track it a little further using malloc(3X), and the
debug-malloc library.  Apparently, there is a malloc somewhere in a
signal handler.  And, if a signal occurs during a malloc elsewhere in
our code, the signal handler malloc does a very good job of destroying
the malloc pointers in the application.

So, it looks like the solution to this problem is to not put mallocs
in your signal handlers.  :-(

Thanks to everyone who offered suggestions.  They helped to track this
one down!

-- 
Dan Rich                    | drich@dialogic.com  || ...!uunet!dialogic!drich
UNIX Systems Administrator  | "Danger, you haven't seen the last of me!"
Dialogic Corporation        |    "No, but the first of you turns my stomach!"
(201) 334-1268 x213         | -- The Firesign Theatre's Nick Danger