Date:	Sat, 16 Jan 93 17:45:53 EST
From:	"Mark W. Eichin" <eichin AT cygnus DOT com>
To:	alane AT wozzle DOT linet DOT org
Cc:	djgpp AT sun DOT soe DOT clarkson DOT edu
Subject:	GNU GDB for DJGPP ?

   SUB: Re: GNU GDB for DJGPP ?
   SUM: <alane AT wozzle DOT linet DOT org>, alane AT wozzle DOT linet DOT org (J. Alan Eldridge)->djgpp AT sun DOT soe DOT clarkson DOT edu

   src4src!mcdhup!rutgers!cogit.ign.fr!dang (Tuan Dang) writes:

   > 
   > I have heard that GDB 4.7 could be used for debugging with DJGPP,
   > I would like to know if anyone has tried it ?

   I sincerely doubt it (DJ, are you listening?). DJ and I have had
   some discussions regarding this topic, and it would be a basic
   architectural change to the extender (go32) in order to support the
   gdb debugger. For now, you have to live with DJ's (excellent) assembly
   language debugger. If it wasn't for lack of real mode memory space,
   we could add C++ name demangling <sigh>.

   alane AT wozzle DOT linet DOT org (J. Alan Eldridge)
   Fido: The University of Walamaloo 1:272/38.473

Another alternative is to use two machines. I've integrated the
gdb i386stub.c (serial remote debugging stub) into debug32; you just
run "dser32 a.out" after using DOS "mode" on com1 to set baud rate and
such. I've single stepped and set breakpoints, list source and
assembly, checked registers (int and float)... everything *should*
work, but I've at least tested many things. It loses badly after stack
corruption (more than it should, I'm afraid) but we've used it to run
compiler and debugger tests, running gdb on a Sun.
	I sent DJ mail about possibly including it in a future release
(the gdb side needs no changes, just configure -target i386-go32...)
but the mail bounced and I haven't tried to get through again. 

					_Mark_ <eichin AT cygnus DOT com>
					Cygnus Support

- Raw text -