Date:	Mon, 17 Jun 1996 10:38:09 +0200 (METDST)
From:	Robert Hoehne <robert DOT hoehne AT Mathematik DOT TU-Chemnitz DOT DE>
To:	DJGPP workers <djgpp-workers AT delorie DOT com>
Subject:	Re: Improvements for GDB
In-Reply-To:	<9606131941.AA13864@clio.rice.edu>
Message-Id:	<Pine.HPP.3.91.960617103044.2278C-100000@newton.mathematik.tu-chemnitz.de>
Mime-Version:	1.0

On Thu, 13 Jun 1996, Charles Sandmann wrote:

> This is actually all available either directly or indirectly in the 
> structure which is returned (how else would the stub know how to do
> it's business if stuff was missing?)

OK. Now I found it by checking 'dbgcom.c'.

> fix for everything is the monitor int 31 approach.  DBGCOM.c already
> monitors int 31 for some events, and the stack usage code that I
> sent to Eli monitors int 31 for cleanup events, so there are a 
> couple of examples around.  If you are going to do it, make it generic,
> put it in dbgcom.c (which already hooks), add a cleanup call.  Then
> all the debuggers (EDEBUG32/FSDB/LDBG/GDB) can all use it if desired.

Over the weekend I did something in this direction. I have now a list
of the memory handles available and I will do it also for the descriptors.

If it is ready I will post it here.

> The debuggers currently disallow hooking any hardware interrupts, since

OK. Was only a question. I'm agree with you, that this realy difficult.

Robert
*****************************************************************
* Robert Hoehne, Fakultaet fuer Mathematik, TU-Chemnitz-Zwickau *
* Post:    Am Berg 3, D-09573 Dittmannsdorf                     *
* e-Mail:  Robert DOT Hoehne AT Mathematik DOT TU-Chemnitz DOT DE              *
* WWW:     http://www.tu-chemnitz.de/~rho                       *
*****************************************************************

- Raw text -