[valgrind] [Bug 392331] Spurious lock not held error from inside pthread_cond_timedwait

https://bugs.kde.org/show_bug.cgi?id=392331 Paul Floyd changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|---

[valgrind] [Bug 392331] Spurious lock not held error from inside pthread_cond_timedwait

https://bugs.kde.org/show_bug.cgi?id=392331 --- Comment #8 from Paul Floyd --- The commit below makes a separate category for this kind of error "Dubious". Please reopen if you also need a command line option. commit 7d0389956e5e6ff182fdf4c2a3a9f8a202a927d4 (HEAD -> master, origin/master,

[valgrind] [Bug 392331] Spurious lock not held error from inside pthread_cond_timedwait

https://bugs.kde.org/show_bug.cgi?id=392331 --- Comment #7 from Jens-W. Schicke-Uffmann --- Regarding user suppression: It would already be very helpful if it could get its own category and would not be reported as Helgrind:Misc Currently, I'm having a suppression which is { Helgrind:Misc

[valgrind] [Bug 392331] Spurious lock not held error from inside pthread_cond_timedwait

https://bugs.kde.org/show_bug.cgi?id=392331 --- Comment #6 from Paul Floyd --- Also TSan does not compain about this g++ -g -o 392331 392331.cpp -pthread -fsanitize=thread ./392331 main() signals data ready for processing Worker thread is processing data Worker thread signals data processing

[valgrind] [Bug 392331] Spurious lock not held error from inside pthread_cond_timedwait

https://bugs.kde.org/show_bug.cgi?id=392331 --- Comment #5 from Paul Floyd --- This message is generated from static void evh__HG_PTHREAD_COND_SIGNAL_PRE ( ThreadId tid, void* cond ) Which looks like the wrapper function called before a pthread_cond_signal And there is the comment // Hmm.

[valgrind] [Bug 392331] Spurious lock not held error from inside pthread_cond_timedwait

https://bugs.kde.org/show_bug.cgi?id=392331 --- Comment #4 from Paul Floyd --- This is rather annoying, especially as it is a bog standard cppreference example and the sort of thing that is likely to occur in any C++11 or later threaded code. -- You are receiving this mail because: You are

[valgrind] [Bug 392331] Spurious lock not held error from inside pthread_cond_timedwait

https://bugs.kde.org/show_bug.cgi?id=392331 Paul Floyd changed: What|Removed |Added CC||pjfl...@wanadoo.fr -- You are receiving this

[valgrind] [Bug 392331] Spurious lock not held error from inside pthread_cond_timedwait

https://bugs.kde.org/show_bug.cgi?id=392331 Jens-W. Schicke-Uffmann changed: What|Removed |Added CC||drahf...@gmx.de --- Comment #3 from

[valgrind] [Bug 392331] Spurious lock not held error from inside pthread_cond_timedwait

https://bugs.kde.org/show_bug.cgi?id=392331 --- Comment #2 from faminebad...@googlemail.com --- > Do you have a small compilable reproducer ? I tried to make a cut-down version, but then it didn't reproduce. Such is the nature of debugging races I guess. However, it's quite clear from the

[valgrind] [Bug 392331] Spurious lock not held error from inside pthread_cond_timedwait

https://bugs.kde.org/show_bug.cgi?id=392331 Philippe Waroquiers changed: What|Removed |Added CC|