[valgrind] [Bug 407764] drd cond_post_wait gets wrong (?) condition on s390x z13 system

2019-05-28 Thread Andreas Arnez
https://bugs.kde.org/show_bug.cgi?id=407764 Andreas Arnez changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|---

[valgrind] [Bug 407764] drd cond_post_wait gets wrong (?) condition on s390x z13 system

2019-05-24 Thread Andreas Arnez
https://bugs.kde.org/show_bug.cgi?id=407764 --- Comment #9 from Andreas Arnez --- (In reply to Mark Wielaard from comment #8) > Also tested on a z13 system with CFLAGS=-march=z13. All wrap tests succeed > and the drd failures are gone. Great! I'll push the patch and close this bug early next

[valgrind] [Bug 407764] drd cond_post_wait gets wrong (?) condition on s390x z13 system

2019-05-24 Thread Mark Wielaard
https://bugs.kde.org/show_bug.cgi?id=407764 --- Comment #8 from Mark Wielaard --- Also tested on a z13 system with CFLAGS=-march=z13. All wrap tests succeed and the drd failures are gone. (except for drd/tests/tc04_free_lock but that fails for a completely unrelated reason). -- You are

[valgrind] [Bug 407764] drd cond_post_wait gets wrong (?) condition on s390x z13 system

2019-05-24 Thread Mark Wielaard
https://bugs.kde.org/show_bug.cgi?id=407764 --- Comment #7 from Mark Wielaard --- Tested on a non-z13 system and all wrap testcases PASS now. -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 407764] drd cond_post_wait gets wrong (?) condition on s390x z13 system

2019-05-23 Thread Andreas Arnez
https://bugs.kde.org/show_bug.cgi?id=407764 Andreas Arnez changed: What|Removed |Added Assignee|bvanass...@acm.org |ar...@linux.ibm.com --- Comment #6 from

[valgrind] [Bug 407764] drd cond_post_wait gets wrong (?) condition on s390x z13 system

2019-05-20 Thread Mark Wielaard
https://bugs.kde.org/show_bug.cgi?id=407764 Mark Wielaard changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0

[valgrind] [Bug 407764] drd cond_post_wait gets wrong (?) condition on s390x z13 system

2019-05-20 Thread Mark Wielaard
https://bugs.kde.org/show_bug.cgi?id=407764 --- Comment #3 from Mark Wielaard --- (In reply to Bart Van Assche from comment #2) > Have you considered to change ", cond" into ", " in the printf() > statement? But cond is already a pointer to a pthread_cond_t. I suspect it is some strange

[valgrind] [Bug 407764] drd cond_post_wait gets wrong (?) condition on s390x z13 system

2019-05-20 Thread Mark Wielaard
https://bugs.kde.org/show_bug.cgi?id=407764 --- Comment #4 from Mark Wielaard --- (In reply to Bart Van Assche from comment #2) > Have you considered to change ", cond" into ", " in the printf() > statement? But cond is already a pointer to a pthread_cond_t. And none of the macros seems to take

[valgrind] [Bug 407764] drd cond_post_wait gets wrong (?) condition on s390x z13 system

2019-05-20 Thread Bart Van Assche
https://bugs.kde.org/show_bug.cgi?id=407764 --- Comment #2 from Bart Van Assche --- Have you considered to change ", cond" into ", " in the printf() statement? -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 407764] drd cond_post_wait gets wrong (?) condition on s390x z13 system

2019-05-20 Thread Mark Wielaard
https://bugs.kde.org/show_bug.cgi?id=407764 --- Comment #1 from Mark Wielaard --- One odd thing is that if you try to add some extra debug statements like: diff --git a/drd/drd_pthread_intercepts.c b/drd/drd_pthread_intercepts.c index d6abd4368..b15b75945 100644 ---