[valgrind] [Bug 430321] drd/tests/bar_bad and drd/tests/bar_bad_xml are non-deterministic

https://bugs.kde.org/show_bug.cgi?id=430321 Yi Fan Yu changed: What|Removed |Added CC||yifan...@windriver.com --- Comment #1 from Yi Fan

[valgrind] [Bug 435160] drd/tests/swapcontext.c: threads are interrupted in nanosleep

https://bugs.kde.org/show_bug.cgi?id=435160 --- Comment #13 from Yi Fan Yu --- https://sourceware.org/git/?p=valgrind.git;a=commit;h=4c8c4a9c3a92300e3e6500e5a278ca37514a1fdb -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 435160] drd/tests/swapcontext.c: threads are interrupted in nanosleep

https://bugs.kde.org/show_bug.cgi?id=435160 Yi Fan Yu changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED

[valgrind] [Bug 435160] drd/tests/swapcontext.c: threads are interrupted in nanosleep

https://bugs.kde.org/show_bug.cgi?id=435160 --- Comment #10 from Yi Fan Yu --- Created attachment 137357 --> https://bugs.kde.org/attachment.cgi?id=137357=edit proposed patch v2 basically to avoid printing the stacktrace with a handled signal. -- You are receiving this mail because:

[valgrind] [Bug 435160] drd/tests/swapcontext.c: threads are interrupted in nanosleep

https://bugs.kde.org/show_bug.cgi?id=435160 --- Comment #9 from Yi Fan Yu --- stderr.exp that would pass the test. ``` Process terminating with default action of signal 14 (SIGALRM) at 0x: clock_nanosleep@@GLIBC_2.17 (clock_nanosleep.c:?) by 0x: nanosleep (nanosleep.c

[valgrind] [Bug 435160] drd/tests/swapcontext.c: threads are interrupted in nanosleep

https://bugs.kde.org/show_bug.cgi?id=435160 --- Comment #7 from Yi Fan Yu --- maybe the root cause is just the stderr.exp being to sensitive... -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 435160] drd/tests/swapcontext.c: threads are interrupted in nanosleep

https://bugs.kde.org/show_bug.cgi?id=435160 --- Comment #6 from Yi Fan Yu --- (In reply to Bart Van Assche from comment #5) > Reverting commit 719d23b7a9c3 ("drd/tests/swapcontext: Improve portability") > is not an option. Valgrind source code must build and run on all suppo

[valgrind] [Bug 435160] drd/tests/swapcontext.c: threads are interrupted in nanosleep

https://bugs.kde.org/show_bug.cgi?id=435160 --- Comment #4 from Yi Fan Yu --- I do know that the commit I reverted mentioned portability. Do you know which platform has problems with timerfd? -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 435160] drd/tests/swapcontext.c: threads are interrupted in nanosleep

https://bugs.kde.org/show_bug.cgi?id=435160 --- Comment #3 from Yi Fan Yu --- Created attachment 137186 --> https://bugs.kde.org/attachment.cgi?id=137186=edit proposed patch revert commit 719d23b7a9c3b02411dee7d5d4d3744938bb768c -- You are receiving this mail because: You are watching

[valgrind] [Bug 435160] drd/tests/swapcontext.c: threads are interrupted in nanosleep

https://bugs.kde.org/show_bug.cgi?id=435160 --- Comment #2 from Yi Fan Yu --- What is the purpose of nanosleep, can it be safely removed? Is there a filter to allow both scenario (stopped in f and stopped in nanosleep) to be correct? -- You are receiving this mail because: You are watching

[valgrind] [Bug 434775] drd/tests/swapcontext.c doesn't build with musl

https://bugs.kde.org/show_bug.cgi?id=434775 Yi Fan Yu changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED

[valgrind] [Bug 435160] drd/tests/swapcontext.c: threads are interrupted in nanosleep

https://bugs.kde.org/show_bug.cgi?id=435160 --- Comment #1 from Yi Fan Yu --- If i remove the nanosleep statement, inside of `f` the original bug report 432381 's error message appears drd: drd_main.c:378 (drd_stop_using_mem): Assertion 'a1 <= a2' failed -- You are receiving this m

[valgrind] [Bug 435160] New: drd/tests/swapcontext.c: threads are interrupted in nanosleep

https://bugs.kde.org/show_bug.cgi?id=435160 Bug ID: 435160 Summary: drd/tests/swapcontext.c: threads are interrupted in nanosleep Product: valgrind Version: unspecified Platform: Other OS: Linux

[valgrind] [Bug 434775] drd/tests/swapcontext.c doesn't build with musl

https://bugs.kde.org/show_bug.cgi?id=434775 --- Comment #3 from Yi Fan Yu --- I tried applying that patch to oe-core build and it still fails with this: So musl does provide as a header, but you cannot link to any of the *context calls. The error is a linker failure. ``` /ala-lpggp31/yyu1/oe

[valgrind] [Bug 400162] Patch: Guard against __GLIBC_PREREQ for musl libc

https://bugs.kde.org/show_bug.cgi?id=400162 Yi Fan Yu changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED

[valgrind] [Bug 400162] Patch: Guard against __GLIBC_PREREQ for musl libc

https://bugs.kde.org/show_bug.cgi?id=400162 Yi Fan Yu changed: What|Removed |Added Attachment #115830|0 |1 is obsolete

[valgrind] [Bug 434775] drd/tests/swapcontext.c doesn't build with musl

https://bugs.kde.org/show_bug.cgi?id=434775 --- Comment #1 from Yi Fan Yu --- Created attachment 136947 --> https://bugs.kde.org/attachment.cgi?id=136947=edit proposed patch (yocto/oe-core fix) -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 434775] New: drd/tests/swapcontext.c doesn't build with musl

https://bugs.kde.org/show_bug.cgi?id=434775 Bug ID: 434775 Summary: drd/tests/swapcontext.c doesn't build with musl Product: valgrind Version: unspecified Platform: Other OS: Linux Status: REPORTED

[valgrind] [Bug 432870] gdbserver_tests:nlcontrolc hangs with newest glibc2.33 x86-64

https://bugs.kde.org/show_bug.cgi?id=432870 --- Comment #10 from Yi Fan Yu --- tested on qemuarm64 and qemux86-64 with glibc2.33 thanks. -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 432870] gdbserver_tests:nlcontrolc hangs with newest glibc2.33 x86-64

https://bugs.kde.org/show_bug.cgi?id=432870 --- Comment #4 from Yi Fan Yu --- here are my findings i summarized to the yocto bugboard. https://bugzilla.yoctoproject.org/show_bug.cgi?id=14223 ## what changed in this patch to cause it to fail? timeout argument the user passes no longer makes

[valgrind] [Bug 432870] gdbserver_tests:nlcontrolc hangs with newest glibc2.33 x86-64

https://bugs.kde.org/show_bug.cgi?id=432870 --- Comment #3 from Yi Fan Yu --- Here is a working call to sleepers *without* the select update patch in 2.33 it used to directly passes timeout to the underlying syscall. With 2.33, it doesn't anymore ``` root@qemux86-64:/usr/lib/valgrind/ptest

[valgrind] [Bug 432870] gdbserver_tests:nlcontrolc hangs with newest glibc2.33 x86-64

https://bugs.kde.org/show_bug.cgi?id=432870 --- Comment #1 from Yi Fan Yu --- this commit for glibc (present in 2.33 but not 2.32) is causing this test to fail when i rebuilt glibc with a patch to revert this commit, the test passes. ``` commit 2433d39b69743f100f972e7886f91a2e21795ef0 Author

[valgrind] [Bug 432870] New: gdbserver_tests:nlcontrolc hangs with newest glibc2.33 x86-64

https://bugs.kde.org/show_bug.cgi?id=432870 Bug ID: 432870 Summary: gdbserver_tests:nlcontrolc hangs with newest glibc2.33 x86-64 Product: valgrind Version: unspecified Platform: Archlinux Packages OS: