Re: [Valgrind-users] Strange errors in backtrace

[Denis P. <dy...@pe...>]

On Thursday 24 July 2003 19:24, Dirk Mueller wrote:
> On Don, 24 Jul 2003, Josef Weidendorfer wrote:
> > shown by valgrind simply means memory access to addresses V can't check
> > because it memory was written to before V switched to its simulated CPU.
>
> ... which would mean that on the given platform/environment the application
> has found a way to escape the valgrind simulated CPU, which must not
> happen.
>
> So it would be very interesting to see a testcase of this problem.

This is SuSE 8.2 with all updates.

I can not simply reproduce this in test case. And I can not give away sources.
But I can do whatever you will tell me to do to find the problem.

You can contact me offlist if you are interested in this, and do not want to
bother others with details.

--
Denis