On 01/18/2013 06:59 AM, Philippe Waroquiers wrote: > 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).
I suspect there's a good reason for it, but I can't remember what it is, and from a quick scan of the lock-order checking code, I can't guess what it is. Philippe hacked on this stuff more recently than me, so he might be able to guess. In any case, at least we have a small test case with the tc14_laog_dinphils test. J ------------------------------------------------------------------------------ Master HTML5, CSS3, ASP.NET, MVC, AJAX, Knockout.js, Web API and much more. Get web development skills now with LearnDevNow - 350+ hours of step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122812 _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
