|
From: Yao Qi <qiy...@cn...> - 2006-02-24 12:30:15
|
On Fri, Feb 24, 2006 at 10:26:37AM +0100, Josef Weidendorfer wrote: > > That seems to be already violated: IMHO, lackey is already advanced tutorial stuff > about detecting memory accesses from VEX code. > And summary vs. trace output makes not a huge difference for a valgrind tool > example. The output is simple, just record every instruction and memory access, but two options in itrace are attractive, --trace-function and --trace-calltree. The former could enable itrace to filter the output and only record instructions in this function you specified, while the latter could enable itrace to record all instructions in this function and instructions in functions called by this function. For example, mostly, we are only interested in instructions in one function, they two could filter the output and only display what you want. > I did not see the source if itrace yet, but a problem to integrate it with > lackey would be if you have a lot of corner cases needing some special > handling, which would make it a bad tutorial. itrace/it_main.c is well-commented and less than 500 lines, and the code itself is simple and neat! We start itrace from lackey, and we could integrate itrace with lackey without breaking its simplicity and readability. I include a patch of valgrind-itrace in attachment, and please apply it to valgrind-3.1.0. [qiyao@plinuxt6 valgrind-3.1.0]$ patch -p1 < ../valgrind-3.1.0-itrace-notests.diff patching file configure.in patching file Makefile.am patching file docs/xml/manual.xml patching file itrace/docs/it-manual.xml patching file itrace/docs/Makefile.am patching file itrace/it_main.c patching file itrace/Makefile.am patching file itrace/tests/Makefile.am I did not add test cases into this patch, and I will submit them later when needed! -- Regards, Yao ------------ Yao Qi |