|embedded dataflow tracking code? firstname.lastname@example.org (Dennis Yurichev) (2010-07-24)|
|Re: embedded dataflow tracking code? email@example.com (George Neuner) (2010-07-26)|
|Re: embedded dataflow tracking code? firstname.lastname@example.org (Gene) (2010-07-26)|
|Re: embedded dataflow tracking code? email@example.com (Tony Finch) (2010-07-27)|
|Re: embedded dataflow tracking code? firstname.lastname@example.org (Walter Banks) (2010-07-30)|
|From:||George Neuner <email@example.com>|
|Date:||Mon, 26 Jul 2010 17:14:07 -0400|
|Organization:||A noiseless patient Spider|
|Posted-Date:||26 Jul 2010 20:40:32 EDT|
On Sat, 24 Jul 2010 12:21:01 -0700 (PDT), Dennis Yurichev
>I would like to load debugger, attach to working process, and at some
>breakpoint, instead of numerical values in the CPU registers, I would
>like to see genesis of each value like "result of f(arg1, arg2,arg3)
>called at point X" or "result of comparison of values X and Y" and so
I don't know of any compiler that tracks register contents in such a
way that a debugger could do that.
Some CPU simulators and inline emulators (hardware) have trace back
buffers for the register contents so you can walk backwards (at least
some way) from the stop to see how the current values came to be that
way. But you still won't see any high level description of the
contents ... there will just be a trace that you can step through
along with the assembler listing.
Return to the
Search the comp.compilers archives again.