Date: Tue, 29 Feb 2000 10:55:55 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Hans-Bernhard Broeker <broeker AT acp3bf DOT physik DOT rwth-aachen DOT de>
cc: djgpp AT delorie DOT com
Subject: Re: Check-Memory
In-Reply-To: <89eesu$kkr$1@nets3.rz.RWTH-Aachen.DE>
Message-ID: <Pine.SUN.3.91.1000229105526.22619C-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
Errors-To: dj-admin AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On 28 Feb 2000, Hans-Bernhard Broeker wrote:

> At least for all libc
> functions written in assembly, stubs would have to be written. Same
> might apply to the 'extern inline' and gcc builtin ones, and all those
> that call OS services that manipulate memory in the program's arena.

Thanks for the info.  But I'm not sure I understand the last part:
what exactly do you mean by ``manipulate memory in the program's
arena''?  DJGPP programs don't manipulate the arena memory in the
usual sense (you can't do that under DPMI), but perhaps you mean
functions that call malloc/free?

Btw, is this documented somewhere?  I cannot seem to find anything in
the GCC docs, but I might be missing something (GCC docs need *lots*
of work in the indexing area, the index is mostly useless).