Xref: news2.mv.net comp.os.msdos.djgpp:6081 From: Robert Hoehne Newsgroups: comp.os.msdos.djgpp Subject: Re: Re RHIDE with integrated debugger. Date: Wed, 17 Jul 1996 14:24:50 +0200 Organization: TU Chemnitz-Zwickau Lines: 31 Message-ID: <31ECDB92.7672@Mathematik.tu-chemnitz.de> References: <01BB7249 DOT 827B0520 AT psp3> NNTP-Posting-Host: tantalus-e.hrz.tu-chemnitz.de Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Steve Higgins wrote: > > 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. > This is not so easy to do. My interface to GDB will be near the above. I link the 'libgdb.a'-library in RHIDE and then I translate the user action to GDB-commands and call the routine 'handle_command' (or so) and I hook the output from GDB for translating it to events in RHIDE. > I would think this would have the advantage of keeping up with the latest > bug fixes/ new features as gdb is updated. This will be also possible with my solution. You need only to relink RHIDE with the new GDB library. > 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. I will think about this. 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 * *****************************************************************