On Tue, Aug 18, 2009 at 9:07 AM, Peng Du<imdup...@gmail.com> wrote: > > Thanks for the hints. The penalty is expected. I've played with PIN and > its pinatrace and MemTrace tools for a while. They worked and the > performance is not too bad, though a bit slower than Valgrind.
That's interesting. The conventional wisdom is that Valgrind is slower than Pin, especially for simple tools like this. > Now I still have a questions: is the memory trace generated by Valgrind > or PIN representative enough to model real program behaviours, considering > multi-threading? Look at the comment at the top of lackey/lk_main.c. Towards the bottom of that comment there is a discussion of the inaccuracies in the memory trace. Nick ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
