Date:	Fri, 19 Aug 94 18:01:26 +1000
From:	junaid AT monu6 DOT cc DOT monash DOT edu DOT au (Mr A. Walker)
To:	djgpp AT sun DOT soe DOT clarkson DOT edu
Subject:	gdb

	I have been playing wihth gdb, and managed to figure out some keys
to use the history and command line ediniting functions.;
(ALT)Q is edit prviouprevious funline
(CTRL)B is non-distructive backspace

	There seems to be a few other keys that haavve lesser utilty.
I suspect that these keyboard mappings are coincidental, and the go32
port of dgdb doesnt bhave any DOS bkeybindings built specifically in.  These
keys probably trigger some dormant key codes....

	Still havent figured out a fix for calling program functions frm
from dgdb.  Howcever calling a functiAlso And because of this there is no way to reliably switswitch from graphics
mode to text and back while debugging.  At the moment i can stop in
mode13 (40x20 bios text emulation), call a functon ion to switch to 80x25
text mode.  Then continuing causes a n illegal instruction fiviolation.

	C-<CTRL)-CC>C results in a FPE violation 'Arithmetic Violation' - perhaps the exception
table has been incorrectly filled in the gthe dgdb source?  Or is this a hack to
get around something?

	Also tho those still struggling;

	go32 -d gdb [program
		
	to debug _program with gdb.  It *is* self evident after reading
the fsdb notes, but should be mensioned in the gdb package.bins.

	So, happy programming all,
	Junaid

- Raw text -