|
From: Chris J. <ch...@at...> - 2004-02-20 11:39:39
|
> "Chris January" <ch...@at...> wrote: > > : Personally I developed this as the foundation for a larger effort to add > : support for program traces/program histories to GDB (using > valgrind + a skin > : called logrind to collect them). > > 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. Chris |