Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!cs.utexas.edu!uunet!jwt!john
From: john@jwt.UUCP (John Temples)
Newsgroups: comp.unix.sysv386
Subject: Re: malloc() problem solved(?)
Message-ID: <1991Apr11.025307.16437@jwt.UUCP>
Date: 11 Apr 91 02:53:07 GMT
References: <1991Apr09.215120.1734@dialogic.com> <1991Apr10.144136.13350@virtech.uucp> <70183@eerie.acsu.Buffalo.EDU>
Organization: Private System -- Orlando, FL
Lines: 10

In article <70183@eerie.acsu.Buffalo.EDU> jones@acsu.buffalo.edu (terry a jones) writes:
>	Or put another way, make sure that your interrupt level code never
>calls routines that are not re-entrant

Is it documented anywhere which system calls are reentrant?  I seem to
recall a thread in another newsgroup about what you can safely to do in
a signal handler, and some people were saying "nothing other than
modifying a global flag and calling signal() to reset the handler."
-- 
John W. Temples -- john@jwt.UUCP (uunet!jwt!john)