delorie.com/archives/browse.cgi | search |
Date: | Sun, 7 Jan 2001 09:19:53 +0200 (IST) |
From: | Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> |
X-Sender: | eliz AT is |
To: | Alain Magloire <alain AT qnx DOT com> |
cc: | djgpp-workers AT delorie DOT com |
Subject: | Re: valloc and memalign draft |
In-Reply-To: | <200101070650.BAA31423@qnx.com> |
Message-ID: | <Pine.SUN.3.91.1010107091835.21289H-100000@is> |
MIME-Version: | 1.0 |
Reply-To: | djgpp-workers AT delorie DOT com |
Errors-To: | nobody AT delorie DOT com |
X-Mailing-List: | djgpp-workers AT delorie DOT com |
X-Unsubscribes-To: | listserv AT delorie DOT com |
On Sun, 7 Jan 2001, Alain Magloire wrote: > I did not follow the thread but malloc and friends cannot be made > async-safe. What you're describing is undefined behaviour or a programming > error i.e. calling a none async-safe routine in a signal handler. malloc isn't documented in DJGPP as non-safe in this context. In DJGPP, signal handlers are called in the normal user context (unlike on Unix), so the handler and the code it runs is generally allowed to do anything that normal C code is allowed to do.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |