[Valgrind-developers] PATCH: Correctly handle threads which switch stacks

[Adam G. <ar...@cy...>]

there are three places where if a thread switches stack, valgrind doesn't
keep its idea of the highest word in the stack in sync. This causes backtraces
with only one function in them, and sometimes causes valgrind to quit.

The attached patch fixes all three cases.


Seeya,
 Adam
--
Real Programmers don't comment their code. If it was hard to write,
it should be hard to read, and even harder to modify.
These are all my own opinions.