[valgrind] [Bug 481679] posix_spawn under valgrind succeeds when it would fail natively due to a missing executable

https://bugs.kde.org/show_bug.cgi?id=481679 Godmar Back changed: What|Removed |Added CC||god...@gmail.com -- You are receiving this mail

[valgrind] [Bug 481679] posix_spawn under valgrind succeeds when it would fail natively due to a missing executable

https://bugs.kde.org/show_bug.cgi?id=481679 Godmar Back changed: What|Removed |Added Platform|Other |Ubuntu -- You are receiving this mail because

[valgrind] [Bug 481679] New: posix_spawn under valgrind succeeds when it would fail natively due to a missing executable

https://bugs.kde.org/show_bug.cgi?id=481679 Bug ID: 481679 Summary: posix_spawn under valgrind succeeds when it would fail natively due to a missing executable Classification: Developer tools Product: valgrind Version: 3.22.0

[valgrind] [Bug 451327] Potential false positive when posting to stack allocated semaphore

https://bugs.kde.org/show_bug.cgi?id=451327 --- Comment #8 from Godmar Back --- (In reply to Godmar Back from comment #7) > It's more reliable if you `NTHREADS` and `n` if you *increase* -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 451327] Potential false positive when posting to stack allocated semaphore

https://bugs.kde.org/show_bug.cgi?id=451327 --- Comment #7 from Godmar Back --- It's more reliable if you `NTHREADS` and `n` -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 451327] Potential false positive when posting to stack allocated semaphore

https://bugs.kde.org/show_bug.cgi?id=451327 --- Comment #5 from Godmar Back --- Created attachment 148434 --> https://bugs.kde.org/attachment.cgi?id=148434=edit test program that shows spurious warning even when threads are joined I've attached a larger example from the actual code to s

[valgrind] [Bug 451327] Potential false positive when posting to stack allocated semaphore

https://bugs.kde.org/show_bug.cgi?id=451327 --- Comment #4 from Godmar Back --- The actual application in which the false positive occurs uses pthread_join properly. I created a minimum reproducible test case here for you to see the issue. Adding pthread_join introduces additional edges

[valgrind] [Bug 451327] Potential false positive when posting to stack allocated semaphore

https://bugs.kde.org/show_bug.cgi?id=451327 Godmar Back changed: What|Removed |Added CC||god...@gmail.com -- You are receiving this mail

[valgrind] [Bug 451327] New: Potential false positive when posting to stack allocated semaphore

https://bugs.kde.org/show_bug.cgi?id=451327 Bug ID: 451327 Summary: Potential false positive when posting to stack allocated semaphore Product: valgrind Version: 3.18.1 Platform: Compiled Sources OS: Linux

[valgrind] [Bug 352130] helgrind reports false races for printfs using mempcpy manipulating FILE* state

https://bugs.kde.org/show_bug.cgi?id=352130 --- Comment #3 from Godmar Back --- I am seeing the same or a very similar issues in valgrind 3.18.1 on Ubuntu 20.04 LTS with GNU LibC 2.5 The attached test program results in: ```c ==952377== Helgrind, a thread error detector ==952377== Copyright (C

[valgrind] [Bug 352130] helgrind reports false races for printfs using mempcpy manipulating FILE* state

https://bugs.kde.org/show_bug.cgi?id=352130 Godmar Back changed: What|Removed |Added CC||god...@gmail.com --- Comment #2 from Godmar Back

[valgrind] [Bug 433497] New: report upper bits of wait(2) status as undefined if `WIFSIGNALED(status)` is true

https://bugs.kde.org/show_bug.cgi?id=433497 Bug ID: 433497 Summary: report upper bits of wait(2) status as undefined if `WIFSIGNALED(status)` is true Product: valgrind Version: unspecified Platform: RedHat RPMs