Re: [Valgrind-users] SysCalls and data flow tracing (problem)

[Nicholas N. <nj...@cs...>]

On Fri, 30 Mar 2007, Frank Naumann wrote:

> Yes that is basically right (I want to instrument each load and store). I
> checked the Ist_Dirty statements (and implemented a Ist_Dirty memory
> tracking). Unfortunately this did not help, since there are no
> reading/writing/modifying Ist_Dirty statements used in this guest
> appliction (and I was already very optimistic, I was realy hoping
> Ist_Dirty is the cause). Well, so I still have the problem.
> All the post/pre_mem_writes use addresses above BEA00000 (not 401E00X). So
> there is no influence from this side.
>
> Is there anything else that can write to the memory? (maybe something I am
> not able to instrument?)

The combination of Ist_Store, Ist_Dirty and pre_mem_write are supposed to 
cover all writes to memory.  It's possible that some are slipping through.
It's also possible that the Valgrind core or Valgrind tool has a bug and is 
writing into the client address space.  I can't think of anything else.

Nick