|
From: Nicholas N. <nj...@ca...> - 2004-02-20 12:53:02
|
On Fri, 20 Feb 2004, Chris January wrote: > > What exactly do you mean by program traces/program histories? Collect > > a full program path trace, like described in Larus' paper (Whole Program > > Paths.) > > No, not quite as described in that paper. I'm thinking more of H. Agrawal, > R. Demillo, and E. Spafford, "Debugging with Dynamic Slicing and > Backtracking," Software-Practice and Experience, Vol.23, No.6, pp.589-616, > 1993, i.e. collecting all reads/writes to registers/memory, function > calls/returns, jumps, etc. (obviously with options to control exactly what > is collected - you only actually need to record writes and jumps to > reconstruct a program's execution) and using the information for dynamic > slicing and similar things. You might be interested in a paper I wrote called "Redux: A dynamic dataflow tracer" (see www.cl.cam.ac.uk/~njn25/pubs.html). It describes a Valgrind tool I wrote that's quite similar to what's described in the Agrawal et al paper. N |