Re: [Valgrind-users] Make Lackey Faster

2009-08-17 Thread Nicholas Nethercote
On Tue, Aug 18, 2009 at 9:07 AM, Peng Du 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 wis

Re: [Valgrind-users] Make Lackey Faster

2009-08-17 Thread John Reiser
> Now I need a very simple memory read/write counting tool, just like > lackey. But the tool has to be fast. Memory is not simple any more. You must precisely define what is a read and what is a write. For example, what is a cache hit (level 1 [L1])? An L2 hit? L3? Coalesced consecutive writes

Re: [Valgrind-users] Make Lackey Faster

2009-08-17 Thread Peng Du
Nick 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. I need the virtual address of the read/write. Hence, HW counters can't do the job. I did c

Re: [Valgrind-users] Make Lackey Faster

2009-08-17 Thread Nicholas Nethercote
On Tue, Aug 18, 2009 at 7:18 AM, Peng Du wrote: > Hello, everyone > > A newbie question, according to Valgrind's manual for the lackey tool: > > "It (lackey) could be made to run a lot faster by doing a slightly more > sophisticated job of the instrumentation ..." > > Now I need a very simple memor

[Valgrind-users] Make Lackey Faster

2009-08-17 Thread Peng Du
Hello, everyone A newbie question, according to Valgrind's manual for the lackey tool: "It (lackey) could be made to run a lot faster by doing a slightly more sophisticated job of the instrumentation ..." Now I need a very simple memory read/write counting tool, just like lackey. But the tool h

Re: [Valgrind-users] Terse description of errors with valgrind 3.4.1

2009-08-17 Thread Dan Kegel
On Thu, Aug 13, 2009 at 1:15 PM, Michel Audette wrote: > See example below. I don't recall details of offending instructions > being replaced by ??? in the past. Is this a new option that I should > be setting, or an indication of a spurious error? > > ==27271== Use of uninitialised value of size 8

Re: [Valgrind-users] Terse description of errors with valgrind 3.4.1

2009-08-17 Thread tom fogal
Michel Audette writes: > Hi Tom, > > thanks for your continued support. np, happy to chime in. Do note that I'm no valgrind dev though, just an interested user. As such, I've cc'd this back to valgrind-users to make sure someone more knowledgeable will read && correct any errors I make; hope y