Re: [Valgrind-users] valgrind analysis of a multi-threaded program

[Julian S. <js...@ac...>]

> I
> find that Helgrind and DRD reports the same - and I see the problems
> very very seldom (similar to memtool) , 


> ==4698==
> Destroying locked mutex: mutex 0x4fc0808, recursion count 1, owner 3.
> ==4698== at 0x490B014: pthread_mutex_destroy
> (drd_pthread_intercepts.c:569)
> ...
> ==4698== by 0x3F05C333A4: exit
> (in /lib64/libc-2.5.so)
> 
> ==4698== by 0x3F05C1D99A: (below main) (in
> /lib64/libc-2.5.so)
> 
> ==4698== mutex 0x4fc0808 was first observed at:
> 
> 
> ==4698== at 0x490AA8D: pthread_mutex_init
> (drd_pthread_intercepts.c:546)
> 
> I must admit, that my insights to
> multi-threaded programming is too sloppy to tell how bad this is.

Destroying a locked mutex could be potentially serious, since it could
be that some other thread is waiting to acquire it, and now (post destroy,
and overwrite of the memory area) can't.  Hence deadlock is a possibility.

J