https://bugs.kde.org/show_bug.cgi?id=400793
Paul Floyd changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REOPENED
https://bugs.kde.org/show_bug.cgi?id=400793
andrey.andreyevic...@gmail.com changed:
What|Removed |Added
Ever confirmed|0 |1
Status|RESOLVED
https://bugs.kde.org/show_bug.cgi?id=400793
Paul Floyd changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=400793
Paul Floyd changed:
What|Removed |Added
CC||pjfl...@wanadoo.fr
--- Comment #2 from Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=400793
--- Comment #1 from Julian Seward ---
This happens because Helgrind on Linux doesn't intercept
pthread_rwlock_timedwrlock and so it doesn't know that the lock has
been taken. The strange thing is, the code to do the intercept
actually exists; it just
https://bugs.kde.org/show_bug.cgi?id=400793
Nikita Leontiev changed:
What|Removed |Added
CC||nikita.leont...@gmail.com
--
You are receivi
https://bugs.kde.org/show_bug.cgi?id=400793
Dmitry Djachenko changed:
What|Removed |Added
CC||dim...@gmail.com
--
You are receiving this
