Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!virtech!cpcahil
From: cpcahil@virtech.uucp (Conor P. Cahill)
Newsgroups: comp.unix.sysv386
Subject: Re: malloc() problem solved(?)
Message-ID: <1991Apr11.122305.3169@virtech.uucp>
Date: 11 Apr 91 12:23:05 GMT
References: <1991Apr09.215120.1734@dialogic.com> <1991Apr10.144136.13350@virtech.uucp> <70183@eerie.acsu.Buffalo.EDU> <1991Apr11.025307.16437@jwt.UUCP>
Organization: Virtual Technologies Inc.
Lines: 26

john@jwt.UUCP (John Temples) writes:

>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."

You can do other things.  But you must ensure that the code you are
executing is

		1) re-entrant

or

		2) it is code that is not normally executed by the rest
		   of your program and you lock out other interrupts while
		   running it.

-- 
Conor P. Cahill            (703)430-9247        Virtual Technologies, Inc.
uunet!virtech!cpcahil                           46030 Manekin Plaza, Suite 160
                                                Sterling, VA 22170