Date: Wed, 13 Jul 94 09:58:15 EDT
From: hvb AT netrix DOT com
To: djgpp AT sun DOT soe DOT clarkson DOT edu
Cc: deastham AT netrix DOT com, esm AT netrix DOT com, jab AT netrix DOT com
Subject: Enhancements to debug32
Reply-To: hvb AT netrix DOT com

Dear all,

We would like to make the following enhancements and bug fixes to
debug32.  We would welcome you to add additional ideas or to let us
know whether it has been fixed in a newer version.

We are currently using debug32 version 1.10.

Debug32 reboot the machine when listing a group of symbols (i.e.
whereis _*, whereis __*, or whereis ___main*, ...)

Debug32's dis-assembler inserts big numbers in source (i.e. mov
eax,[ebx] becomes mov eax,[ebx+57085041].)

When a dump statement is executed, and a segment violation occured,
Debug32 would not be able to continue its execution.

When a set or display memory statement is executed and returns a
segment violation error, Debug32 would not be able to continue running
the program.

Cls command (in Debug32) always set the screen to 80x25 regardless
what value is set by th=..

Debug32 can not locate a module with the leaf name of the source
module, it needs the full pathname.
Enhancement:
Leaf name of a source module can be specified and any duplicated
references can be prompted and resolved.

The display memory command needs to be able to display byte, 16-bit
word, 32-bit word format.

It would be nice to be able to access and execute the last <n> commands.

The break point handling needs to be more flexible: increase the
number of break points, allow passing break point, and a break point count.