https://bugs.kde.org/show_bug.cgi?id=374414
--- Comment #5 from Yuval Lifshitz <yuva...@yahoo.com> ---
didn't say that wake-up is not missed. but the program would still perform
correctly, since the protected variables "ready" and "processed" are either
being checked
https://bugs.kde.org/show_bug.cgi?id=374414
--- Comment #3 from Yuval Lifshitz <yuva...@yahoo.com> ---
what about the following case:
we change:
cv.wait(lk, []{return ready;});
to (which should be similar):
while (!ready) cv.wait(lk);
in this case, as long as there is only one thread w
https://bugs.kde.org/show_bug.cgi?id=374414
Bug ID: 374414
Summary: unlocking mutex before calling notify_one/all on
condition variable triggers an error
Product: valgrind
Version: 3.10.0
Platform: Debian stable
