Re: Ok sorry, it is just a book gives no feedback.

[Marin David Condic <mcondic.nospam@acm.org>]

Larry Kilgallen wrote:

> Been there, done that, got the T-shirt.  I detested it.
> I think one of the great debugger advances has been to
> use a small engine in the process being debugged and
> put the great bulk of the debugger (GUI, etc.) into
> another process where it will not impact addresses,
> etc.  (Of course that does not eliminate the heisenbug

I am presuming that you are talking about having a relatively small chunk of code in an
embedded app that will grab the contents of memory and send it down the wire upon request,
etc.? The concept of an on-board monitor that will load & read memory, maintain lists of
addresses to watch & report on periodically, etc. has been around for a while. They work very
nicely - especially since they remain in the production code/box so that you can actually use
them in the field if necessary. You don't need any special equipment besides the presence of
a communication link.

Granted, they do consume some of the available CPU time and may impact timing issues, but
they work very well for debugging in environments where you don't have specialized hardware
or Text_IO.

MDC
--
======================================================================
Marin David Condic - Quadrus Corporation - http://www.quadruscorp.com/
Send Replies To: m c o n d i c @ q u a d r u s c o r p . c o m
Visit my web site at:  http://www.mcondic.com/

    "Giving money and power to Government is like giving whiskey
    and car keys to teenage boys."

        --   P. J. O'Rourke
======================================================================