X-Authentication-Warning:	delorie.com: mailnull set sender to djgpp-workers-bounces using -f
From:	sandmann AT clio DOT rice DOT edu (Charles Sandmann)
Message-Id:	<10205162025.AA14430@clio.rice.edu>
Subject:	Re: emacs under w2k
To:	djgpp-workers AT delorie DOT com
Date:	Thu, 16 May 2002 15:25:51 -0500 (CDT)
Cc:	lauras AT softhome DOT net (Laurynas Biveinis)
In-Reply-To:	<7999-Thu16May2002220929+0300-eliz@is.elta.co.il> from "Eli Zaretskii" at May 16, 2002 10:09:29 PM
X-Mailer:	ELM [version 2.5 PL2]
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

> > Do I need unixy sbrk flag in this case?
> 
> No, you don't.  But you could try with and without it, if Charles
> thinks its will be useful.

I have no idea if it's useful yet.  If we are dieing in sbrk(), this
is the one bit which radically changes sbrk() behavior.

Note, you can clear the unixy sbrk bit, on the fly, and do all future
allocations in non-move manner.  But don't set the bit after startup
with it clear, or you will certainly crash.

So, if you start in the debugger, you can modify this flag while debugging
the exact same binary, same place in debug process to see if the same
line crashes same way, or differently (or not at all...).

Since the debugger can allocate memory also, worse case is they end up
with blocks interlevened between debugger, application, debugger, app.
With unixy sbrk, app can't be non-contiguous, so it physically moves
the application in memory.  Just beware.

- Raw text -