|
From: Jeremy F. <je...@go...> - 2003-09-24 14:31:15
|
On Mon, 2003-09-15 at 21:19, Stefan Nilsson wrote: > Hi, I'm using Valgrind on a multithreaded application, and after all > threads are created and set off, I get the following assert: > > assert(mx->__m_count > 0) This is pretty much a bogus assertion. "mx" is the pointer to the client's mutex structure, and Valgrind can't really assert anything about it, since it could be being merrily trashed by the client. I think it's a bit fragile for Valgrind to be relying on mutex state stored within the mutex itself. Helgrind uses shadow mutex structures for this reason. J |