|embedded dataflow tracking code? email@example.com (Dennis Yurichev) (2010-07-24)|
|Re: embedded dataflow tracking code? firstname.lastname@example.org (George Neuner) (2010-07-26)|
|Re: embedded dataflow tracking code? email@example.com (Gene) (2010-07-26)|
|Re: embedded dataflow tracking code? firstname.lastname@example.org (Tony Finch) (2010-07-27)|
|Re: embedded dataflow tracking code? email@example.com (Walter Banks) (2010-07-30)|
|Date:||Mon, 26 Jul 2010 16:24:38 -0700 (PDT)|
|Posted-Date:||26 Jul 2010 20:41:37 EDT|
On Jul 24, 3:21 pm, Dennis Yurichev <dennis.yuric...@gmail.com> wrote:
> 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
> Probably, compiler backend could embed some dataflow tracking code
> between basic blocks and store information about all variables flow in
> some separate data segment..
> Are there any known attempts or projects or...?
At one point Borland debuggers offered the capability to step backward
from a breakpoint. (I don't know if this is still true.) I recall one
could graphically depict the backward control flow in the source. It
appeared this was done entirely in the debugger, as no recompilation
was ever necessary to use the feature. It seemed likely to me that the
debugger must have been trapping every instruction and maintaining a
trace of branch sources and overwritten data. The trace was consulted
in backward order to do the reverse stepping. It sounds like you are
proposing that the compiled program do the same thing. I guess there
could be some performance advantage in maintaining the trace without
I obtained more insight by finding the right Google term, which is
"reverse execution." Borland called it this in 1991-1992. Apparently
it's now a feature in GDB v7 and other modern debuggers, which seem to
have re-discovered it only lately.
Return to the
Search the comp.compilers archives again.