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

2017-05-09 Thread Siddharth Nilakantan
Oops. I started typing my response and then decided to respond inline. Forgot to delete my partial original response. :) On 9 May 2017 at 12:36, Siddharth Nilakantan wrote: > Hi Ivo, > > The goal is to get at the > > Thanks, > Sid > > On 9 May 2017 at 00:48, Ivo Raisr wrote: > >> 2017-05-08 20:

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

2017-05-09 Thread Siddharth Nilakantan
Hi Ivo, The goal is to get at the Thanks, Sid On 9 May 2017 at 00:48, Ivo Raisr wrote: > 2017-05-08 20:39 GMT+02:00 Siddharth Nilakantan : > > Hi Mike and Ivo, > > > > I noticed a thread where you guys had a discussion going. > > > > https://sourceforge.net/p/valgrind/mailman/message/35687503/

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

2017-05-08 Thread Ivo Raisr
2017-05-08 20:39 GMT+02:00 Siddharth Nilakantan : > Hi Mike and Ivo, > > I noticed a thread where you guys had a discussion going. > > https://sourceforge.net/p/valgrind/mailman/message/35687503/ > > I was playing around with writing a tool that does some online analysis of > register reads/writes.

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

2017-03-02 Thread Ivo Raisr
2017-03-03 0:01 GMT+01:00 Mike Lui : > 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 >

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

2017-03-02 Thread Mike Lui
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-too

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

2017-03-02 Thread Ivo Raisr
2017-03-02 23:07 GMT+01:00 Mike Lui : > Hi Ivo, > > I didn't get a response, but I found a snippet in the original paper: > https://www.cs.columbia.edu/~junfeng/09fa-e6998/papers/valgrind.pdf > > Table 1 says these functions are only for syscalls and the valgrind core. Is > that still correct? Hi

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

2017-03-02 Thread Mike Lui
Hi Ivo, I didn't get a response, but I found a snippet in the original paper: https://www.cs.columbia.edu/~junfeng/09fa-e6998/papers/valgrind.pdf Table 1 says these functions are only for syscalls and the valgrind core. Is that still correct? Mike On Thu, Mar 2, 2017 at 4:28 PM Ivo Raisr wrote

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

2017-03-02 Thread Ivo Raisr
2017-02-25 3:55 GMT+01:00 Mike Lui : > Being unable to search through gmane for now, I turn to the users group. > > I'd like some clarification regarding some functions I'm seeing in the tool > interface. > > track_new_mem_startup > > track_new_mem_mmap > ... > track_pre_mem_read > track_pre_m