Re: Helgrind causing data race warning in mutex_destroy_WRK?

> >
> > To me it seems that Helgrind itself is causing the warning when
> > calculating mutex_is_init (hg_intercepts.c:859).
> 
> Isn't this rather a race between unlocking a mutex and destroying that mutex?

I'm not sure... I know it's not a very strong argument, but the Poco::Timer code is not that complex, and I could not find anything wrong with it.

What puzzles me is that the location Helgrind reports is "inside" the mutex object itself. Is it even possible to create a race on the memory location of a mutex, when only accessing it through the pthread_mutex_* API?