Date: Wed, 3 Jan 2001 10:53:12 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Martin Str|mberg <ams AT ludd DOT luth DOT se>, djgpp-workers AT delorie DOT com
Subject: Re: GO32=topline
In-Reply-To: <2561-Tue02Jan2001204558+0200-eliz@is.elta.co.il>
Message-ID: <Pine.SUN.3.91.1010103105240.1129L-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
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
Precedence: bulk


On Tue, 2 Jan 2001, I wrote:

> As DJ says, some of the info is avaiable in various low-level places
> of the library, like sbrk and __dpmi_int, but that's not bullet-proof,
> since someone may issue the relevant instructions directly in inline
> assembly.

There's also another, more painful case when hooking on the libc level
won't do: when you have nested programs.  All you see inside the
library is what your program does, but not what the children do.

To solve this on the application level, you'd need to hook Int 31h and
filter the calls, like dbgcom.c does.  That's painful and slow.