From:	Martin Str|mberg <ams AT ludd DOT luth DOT se>
Message-Id:	<200101070740.IAA22361@father.ludd.luth.se>
Subject:	Re: valloc and memalign draft
In-Reply-To:	<Pine.SUN.3.91.1010107091835.21289H-100000@is> from Eli Zaretskii at "Jan 7, 2001 09:19:53 am"
To:	djgpp-workers AT delorie DOT com
Date:	Sun, 7 Jan 2001 08:40:40 +0100 (MET)
X-Mailer:	ELM [version 2.4ME+ PL54 (25)]
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

According to Eli Zaretskii:
> 
> 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.

Ooooh!!! DJGPP is _better_ than Unix!


Right,

						MartinS

- Raw text -