Re: [Valgrind-developers] vmware backdoor patch

[Sunny D. <int...@ya...>]

Those invalid reads are from pth and are understood to be safe to ignore.


I had tried 3.7.0 while debugging the earlier issue but reverted back to stable to reduce the moving parts. May be, now that I am past the backdoor, I can go back to 3.7.0.

-Sunny


----- Original Message -----
From: Philippe Waroquiers <phi...@sk...>
To: Sunny Das <int...@ya...>
Cc: "val...@li..." <val...@li...>
Sent: Thursday, June 7, 2012 1:17 PM
Subject: Re: [Valgrind-developers] vmware backdoor patch

On Thu, 2012-06-07 at 12:33 -0700, Sunny Das wrote:
> Looks like process died, not the valgrind. Other than that message in the end,
>  the log file consists of backtraces of usual 'invalid reads'
Also, invalid reads should better be fixed (or at least understood and
proved "safe"), as these invalid reads might cause e.g. access to
unmapped memory, causing a SEGV.
Again, the 3.7.0 V gdbserver will help to understand what is going on.

Philippe