https://bugs.kde.org/show_bug.cgi?id=498936
Paul Floyd changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=498936
--- Comment #4 from Tavian Barnes ---
I guess? I'm surprised that valgrind will totally starve a thread by default.
This may be a dupe of https://bugs.kde.org/show_bug.cgi?id=343357 anyway.
--
You are receiving this mail because:
You are watching al
https://bugs.kde.org/show_bug.cgi?id=498936
--- Comment #3 from Paul Floyd ---
(In reply to Tavian Barnes from comment #2)
> --fair-sched=yes seems to work around it
OK, can we close this item?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=498936
--- Comment #2 from Tavian Barnes ---
--fair-sched=yes seems to work around it
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=498936
Paul Floyd changed:
What|Removed |Added
CC||pjfl...@wanadoo.fr
Assignee|jsew...@acm.
https://bugs.kde.org/show_bug.cgi?id=498936
--- Comment #1 from Tavian Barnes ---
Okay here's a more reduced testcase:
```
#include
#include
atomic_bool start, stop;
void *work(void *ptr) {
start = 1;
while (!stop);
return NULL;
}
int main(void) {
pthread_t t
