From owner-freebsd-bugs Wed Jan 1 11:30:04 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA20236 for bugs-outgoing; Wed, 1 Jan 1997 11:30:04 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA20227; Wed, 1 Jan 1997 11:30:01 -0800 (PST) Date: Wed, 1 Jan 1997 11:30:01 -0800 (PST) Message-Id: <199701011930.LAA20227@freefall.freebsd.org> To: freebsd-bugs Cc: From: Garrett Wollman Subject: Re: bin/2347: sysinstall: ppp: recursive call in malloc() Reply-To: Garrett Wollman Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk The following reply was made to PR bin/2347; it has been noted by GNATS. From: Garrett Wollman To: Poul-Henning Kamp Cc: freebsd-gnats-submit@freefall.freebsd.org Subject: Re: bin/2347: sysinstall: ppp: recursive call in malloc() Date: Wed, 1 Jan 1997 14:25:20 -0500 < said: > I'm not definitively sure what POSIX & friends say about the reentrancy > of malloc(3) but I belive it is not required to be reentrant. > Anybody know definitively what POSIX say here ? Well, I can't tell you what POSIX says, but I can tell you what ANSI X3J11 said: the only thing you can do inside a signal handler is set a variable of type `volatile sig_atomic_t'. Hearsay: one of the UNIX standards (maybe P1003.n, maybe XPGn, maybe Spec 1170) specifies a list of *system calls* which may be called from signal handlers. I think one or more of them may also require that longjmp() work from a signal handler, but not necessarily that anything work after doing that. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, ANA, or NSA| - Susan Aglukark and Chad Irschick