Re: [Valgrind-users] Helgrind and "stack unavailable"

[Philippe W. <phi...@sk...>]

On Thu, 2013-01-17 at 19:00 +0000, Phil Longstaff wrote:

> What is the cause of “stack unavailable”?  This error message doesn’t
> give me enough information to go on, since it doesn’t tell me anything
> about what the first incorrectly locked mutex is or about the stacks
> establishing the correct locking order.
I suspect this can happen when the (invalid) locking chain is complex 
(e.g. sequences more complex than lockA,lockB and lockB,lockA).

Not digged more in depth. There is a small helgrind regression test
which causes also this output (helgrind/tests/tc14_laog_dinphils.vgtest).

Would be nice to investigate further ...

Philippe