18 Mar
2010
18 Mar
'10
2:44 p.m.
Just a thought
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 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.
Randy
From: cclist at sydex.com
To: cctalk at classiccmp.org
Date: Thu, 18 Mar 2010 14:21:38 -0700
Subject: Re: Disc analyser news update
On 18 Mar 2010 at 19:33, Tony Duell wrote:
_________________________________________________________________
Hotmail: Trusted email with powerful SPAM protection.
http://clk.atdmt.com/GBL/go/210850553/direct/01/
And a logic analyser will tell you different
things to a breakpoint.
OK, at a breakpoint (if the debugging hardware is designed sensibly),
you can exame CPU registers, etc. But it woun't necessarily tell you
how the code got to the breakpoint. A logic analyser will/
Hardly! Maybe on vintage CPUs, but not on anything made in the last
20 years. Caching, prefetch queues, scheduling hardware and
integrated peripherals make a logic analyzer of marginal use in
debugging program flow.
Times have changed and so have methods. For example, simulation is
used a lot more than it used to be for designs, as is on-chip
debugging support.
--Chuck