Re: [Valgrind-users] Clarification on functions in pub_tool_tooliface.h

[Ivo R. <iv...@iv...>]

2017-03-03 0:01 GMT+01:00 Mike Lui <mik...@gm...>:
> I did a poor job explaining my inquiry. I'm writing a valgrind tool that's
> tracking the IOPS/FLOPS/reads/writes reported by VEX IR during
> instrumentation, and doing some minor analysis on the IR with a
> instrument_basic_block callback (as documented in
> http://www.valgrind.org/docs/manual/writing-tools.html)

That is interesting. How are you going to represent the results?
Cannot be the existing tools "persuaded" to do what you need?

> So my understanding right now is that as long as a syscall wrapper exists,
> registering to *_mem_write will give me metadata about userspace memory
> modified by supported syscalls, otherwise I use the normal
> instrument_basic_block callback.

Alright.

I.