https://bugs.kde.org/show_bug.cgi?id=445504
--- Comment #2 from nikol...@rath.org --- With Valgrind 3.18.1, the error becomes ==872160== Helgrind, a thread error detector ==872160== Copyright (C) 2007-2017, and GNU GPL'd, by OpenWorks LLP et al. ==872160== Using Valgrind-3.18.1 and LibVEX; rerun with -h for copyright info ==872160== Command: ./valgrind_test ==872160== [...] ==872160== Thread #1 unlocked lock at 0x1FFF000090 currently held by thread #2 ==872160== at 0x4841D06: ??? (in /usr/libexec/valgrind/vgpreload_helgrind-amd64-linux.so) ==872160== by 0x10B946: __gthread_mutex_unlock(pthread_mutex_t*) (in <redacted>/valgrind_test) ==872160== by 0x10BB8D: std::mutex::unlock() (in <redacted>/valgrind_test) ==872160== by 0x10C652: std::lock_guard<std::mutex>::~lock_guard() (in <redacted>/valgrind_test) and ==872482== drd, a thread error detector ==872482== Copyright (C) 2006-2020, and GNU GPL'd, by Bart Van Assche. ==872482== Using Valgrind-3.18.1 and LibVEX; rerun with -h for copyright info ==872482== Command: ./valgrind_test ==872482== Other thread: waiting for notify ==872482== The impossible happened: mutex is locked simultaneously by two threads: mutex 0x1fff000090, recursion count 1, owner 2. ==872482== at 0x484B478: pthread_mutex_lock (in /usr/libexec/valgrind/vgpreload_drd-amd64-linux.so) ==872482== by 0x10B917: __gthread_mutex_lock(pthread_mutex_t*) (in <redacted>/valgrind_test) ==872482== by 0x10BB5F: std::mutex::lock() (in <redacted>/valgrind_test) ==872482== by 0x10C633: std::lock_guard<std::mutex>::lock_guard(std::mutex&) (in <redacted>/valgrind_test) -- You are receiving this mail because: You are watching all bug changes.
