https://bugs.kde.org/show_bug.cgi?id=501713
Paul Floyd <pjfl...@wanadoo.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |pjfl...@wanadoo.fr
--- Comment #2 from Paul Floyd <pjfl...@wanadoo.fr> ---
(In reply to zephyrus00jp from comment #1)
> So maybe newer versions of valgrind has issue(s) [maybe it does not handle
> thread sync related primtives correctly? Maybe hellgrind does and memcheck
> forgets to handle some primitives?].
> Or thunderbird does something wrong which firefox gets right.
I don't see anything concrete here that indicates a bug in Valgrind. Memcheck
has detected a conditional read error. I strongly suggest that you take
memcheck's word that there is an error and don't start making random guesses
about other causes.
It is possible that the change in scheduling that you get when running under
Valgrind is revealing an underlying bug in the guest code. That's still a guest
issue. The Valgrind core has to do some hacky things so that newly spawned
threads also run under Valgrind. Memcheck doesn't do anything else with thread
primitives. DRD and Helgrind intercept pthread functions so that they an
validate and record the thread state. The intercepts still call the intercepted
pthread functions.
In order to see where the error is try using vgdb. You will need 2 terminals,
one with valgrind and the other with gdb. When you hit the error you can use
the memcheck monitor commands to see which part of the 'if' expression is
uninitialized.
--
You are receiving this mail because:
You are watching all bug changes.
