[Valgrind-users] Message about error in pthread_mutex_unlock useless

[<ar...@fl...>]

Hi.

I am the current valgrind maintainer for Debian. A Debian user has request this feature
which could be good to have if is possible. Below is the email.

Best regards.


--- snip ---

hello,

valgrind detects the following error in my code:
==10840== Thread 6:
==10840== pthread_mutex_unlock: mutex is locked by a different thread
==10840==    at 0x40347B3A: __pthread_mutex_unlock (vg_libpthread.c:980)
==10840==    by 0x40347B73: __pthread_mutex_destroy
(vg_libpthread.c:1001)
==10840==    by 0x4020BCA1: __MSG_context_destroy (msg_context.c:110)
==10840==    by 0x4020B95D: __MSG_process_launcher (msg_context.c:63)
==10840==    by 0x40347412: thread_wrapper (vg_libpthread.c:671)
==10840==    by 0x40161280: do__quit (vg_scheduler.c:2154)

That's very well and good, but I cannot debug this case, because I do
not know which other thread does lock this mutex.

I know I should review my code and find it myself, but it would be very
usefull if valgrind could report which other thread it is.

I think about a message like:
==10840== Thread 6:
==10840== pthread_mutex_unlock: mutex is locked by thread 4


I have no idea of how hard it would be, but it would be really great.

Thanks for this wonderful tool, Mt.


--- snip ---

--
Andres Roldan, CSO
Fluidsignal Group