Re: [Valgrind-users] valgrind pthreads mutex bug

[Jeremy F. <je...@go...>]

On Thu, 2003-05-29 at 16:23, Andraz Tori wrote:

> Maybe worth mentioning is, that thread 25 wasn't the thread that created
> & locked the mutex at the first place, but this should not be an issue,
> since this is vaild behaviour in pthreads.

No it isn't.  You can't lock with one thread and unlock with another -
pthread_mutex_unlock should return EPERM (calling thread does not own
mutex).

The bug is that Valgrind should flag this as an error.

    J