Re: pthread_mutex_destroy with invalid argument

On 2021-12-21 20:07, Casey Waldren via Valgrind-users wrote:
> Hello,
>
> I am running into the following errors when running helgrind on a C++ 
> binary built with googletest. The host is Ubuntu 20.04.
>
> The invocation is:
>
> valgrind --tool=helgrind --error-exitcode=100 ./tests/google_tests
>
> The errors are:
>
> ---Thread-Announcement------------------------------------------ 
> ==947== ==947== Thread #1 is the program's root thread ==947== ==947== 
> ---------------------------------------------------------------- 
> ==947== ==947== Thread #1: pthread_mutex_destroy with invalid argument 
> ==947== at 0x483FC96: ??? (in 
> /usr/lib/x86_64-linux-gnu/valgrind/vgpreload_helgrind-amd64-linux.so) 
> ==947== by 0x5AD316F: ??? (in 
> /usr/lib/x86_64-linux-gnu/libp11-kit.so.0.3.0) ==947== by 0x4011F5A: 
> _dl_fini (dl-fini.c:138) ==947== by 0x4D12A26: __run_exit_handlers 
> (exit.c:108) ==947== by 0x4D12BDF: exit (exit.c:139) ==947== by 
> 0x4CF00B9: (below main) (libc-start.c:342) ==947== ==947== 
> ---------------------------------------------------------------- 
> ==947== ==947== Thread #1: pthread_mutex_destroy with invalid argument 
> ==947== at 0x483FC96: ??? (in 
> /usr/lib/x86_64-linux-gnu/valgrind/vgpreload_helgrind-amd64-linux.so) 
> ==947== by 0x4011F5A: _dl_fini (dl-fini.c:138) ==947== by 0x4D12A26: 
> __run_exit_handlers (exit.c:108) ==947== by 0x4D12BDF: exit 
> (exit.c:139) ==947== by 0x4CF00B9: (below main) (libc-start.c:342)
> I am wondering if anyone has seen this or can shed some light on what 
> these imply? I used --tool=drd and it failed with almost identical 
> errors.


Hi

Which version of Valgrind is this with?

I've been trying to do some cleanup of C++ and DRD/Helgrind, but I 
haven't seen this sort of problem.

This looks like pthread_mutex_destroy being called from a destructor. 
Can you provide a simple reproducer?


A+

Paul