|
From: Siddharth N. <si...@gm...> - 2013-01-04 21:40:18
|
Hi All, I am trying to instrument syscalls that read from and modify memory. I want to use the pre_mem_read and post_mem_write functions, but I also need the correct function execution context when the read and write occurs (user program function where the syscall occurs). So my idea was to use Callgrind, record all pre_mem_reads and query the context during the next syscall and similarly during post_mem_writes query the context of the previous syscall that has occurred. I couldn't find any documentation on how pre_mem_read functions work in conjunction with syscalls. Am I going about this right? Thanks, Siddharth |
|
From: Siddharth N. <si...@gm...> - 2013-01-16 00:07:44
|
Hi All, Any word on this? Let me re-phrase in a less complicated way: Do pre_mem_reads indicate the addresses that will be read by the next executed syscall? Essentially, how do you match pre_mem_reads to syscalls (and post_mem_writes to syscalls)? How would one count the number of instructions that occur during a syscall? Thanks, Siddharth On 4 January 2013 16:39, Siddharth Nilakantan <si...@gm...> wrote: > Hi All, > > I am trying to instrument syscalls that read from and modify memory. I > want to use the pre_mem_read and post_mem_write functions, but I also > need the correct function execution context when the read and write > occurs (user program function where the syscall occurs). > > So my idea was to use Callgrind, record all pre_mem_reads and query > the context during the next syscall and similarly during > post_mem_writes query the context of the previous syscall that has > occurred. I couldn't find any documentation on how pre_mem_read > functions work in conjunction with syscalls. Am I going about this > right? > > Thanks, > Siddharth > |