|
From: Tom H. <to...@co...> - 2006-09-07 14:10:04
|
In message <115...@ok...>
Alex Bennee <ker...@be...> wrote:
> On Thu, 2006-09-07 at 10:31 +0100, Alex Bennee wrote:
>> On Wed, 2006-09-06 at 18:49 +0100, Tom Hughes wrote:
>> > In message <115...@ok...>
>> > Alex Bennee <al...@tr...> wrote:
>> Sorry the pid mentioned in getLock is a value stored in our task
>> structure. It is only ever set in the setPid(0 function and after that
>> is a read only value.
>
> Additionally running the program native with the instrumentation never
> clobbers the pid variable to 0. I think this points more towards a a bug
> with Valgrind.
I think it's very unlikely. I can't think of a single case of such a
bug in valgrind where it was wrongly writing to client memory.
Or are you suggesting a translation error so that valgrind is
producing incorrect code? Those are pretty rare as well...
Far more likely is that running under valgrind has changed the
layout of memory in your program so that an existing problem in
your program is manifesting itself by overwriting something more
important.
> Is there a way to log the loads and stores valgrind makes?
No. I'm not even entirely sure what loads and stores you are talking
about, but the answer is no anyway.
Tom
--
Tom Hughes (to...@co...)
http://www.compton.nu/
|