18 Mar
2010
18 Mar
'10
2:52 p.m.
On Mar 18, 2010, at 5:44 PM, Randy Dawson wrote:
Code debug probably is done best in a virtual machine,
or an emulator where you can instrument the heck out of it.
There once was 'bond out' intel (and other) cpus specifically for emulation /
debug. You got hardware signal access to the internal registers and state of the machine.
I have some bondout chips in my mcs51 emulator, for the Philips P89C66x chips. They
give you direct access to the signals that Tony is complaining about being inaccessible.
I also recall that TASM could remotely debug over a
network connection so the target could run at full speed, Im sure all modern Visual C++ or
gnu debug can do the same.
Yes, gdb can.
-Dave
--
Dave McGuire
Port Charlotte, FL