Message-ID: <01BB7249.827B0520@psp3>
From: Steve Higgins <steve AT psp-digital DOT co DOT uk>
To: "'DJGPP Mail List'" <djgpp AT delorie DOT com>
Subject: Re RHIDE with integrated debugger.
Date: Mon, 15 Jul 1996 12:31:05 -0000
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit


Robert Hoehne write :-

>GDB is a very powerfull debugger and it has so many functions that it
>is not possible for me, to support all of them within RHIDE. Now at the
>first the state of my work I can set breakpoints
>(also with conditions and counts) and I can examine variables (watch
>and modify).

As I understand it, GDB just uses the standard input/output to communicate
with the outside world.

So rather than re-inventing the wheel, would it be possible to intercept the
relevent int 21h routines, spawn GDB, then write the code to translate the 
data sent to and from the standard i/o into your RHIDE display updates etc.

I understand that in the un*x world there are a number of gdb front ends,
including the emacs front end, written in this way (they are able to use 
pipes of course!). 

I would think this would have the advantage of keeping up with the latest
bug fixes/ new features as gdb is updated. You could also give the option
of opening a window giving direct access to the gdb input and output data
so if I want access to a feature not supported in RHIDE I could just open
this window.

Regards

Steve.