|
From: Yao Qi <qiy...@cn...> - 2006-02-23 05:32:09
|
I would like to send this request to maillist for an open discussion. Geoff Smith proposed an idea about Instruction Trace at http://sourceforge.net/mailarchive/message.php?msg_id=14760370 and I would like to explain and advocate his proposal. We started to write this tool in December 2005, and finish the prototype based on valgrind-3.1.0 until now. valgrind-itrace could trace actually executed instructions and record memory access, and output the result in a simple plain text format. It would work on X86 and PPC32 well. On the other hand, itrace/it_main.c is simple, less 500 lines, so it could be understood easily and help developers understand Valgrind internals. In this survey http://valgrind.org/gallery/survey_05/report.txt, it is said that, Profiling: - the possibility to perform the combination of instruction, syscall, and cache instrumentation. 1 Simulation correctness/robustness - Better instruction set coverage 5 function call tracer 3 so itrace in valgrind could do something relative to that above, and we are interested in contributing it to valgrind community and continue to improve its code , test cases and document. I do appreciate your comments at your earliest convenience, and I will submit a patch if you are willing to have a look on it. Thanks! -- Regards, Yao ------------ Yao Qi |