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 <iv...@ivosh.net> wrote:
2017-02-25 3:55 GMT+01:00 Mike Lui <mike.d....@gmail.com>:
> 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_mem_write
> track_post_mem_write
> track_post_reg_write
>
> These callbacks specifically refer to events within the core, right? Does
> this mean that they bear no relevance to profiling the user application?
>
> Am I correct that a "mem_write" callback only gets called for memory write
> that happens during translation, internal signal handling, etc, along with
> the "new_mmap" calls? If I were to instrument the application under test
> then I'd go through the callback given in "basic_tool_funcs", correct?
>
> I only asks because I just noticed these functions, and the wording in the
> comments wasn't incredibly clear.
Did you get any response for your query? If not, I will chime in.
I.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Valgrind-users mailing list
Valgrind-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-users
