Rui Paulo a écrit :

> Unlocking an unlocked mutex is, obviously, not correct :-) The point
> of that message is to detect mutex problems.
> You can ignore it by setting the environmental variable
> PTHREAD_DIAGASSERT to 'A'. See pthread(3) for more info.

Yep, that's what I did. But, if I admit gracefully that it is obviously 
NOT correct, is it, for example, more critical than to free an already 
freed chunck of memory? The latter case is, as far as I know, (quite 
always) treated as a warning and not as an error…

Vincent