[valgrind] [Bug 439082] memcheck/tests/linux/stack_changes fails on qemuarm64 builds
https://bugs.kde.org/show_bug.cgi?id=439082 Mark Wielaard changed: What|Removed |Added CC||[email protected] Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #5 from Mark Wielaard --- We are suddenly seeing this on fedora 40, 41 and eln: https://kojipkgs.fedoraproject.org//packages/valgrind/3.23.0/4.fc40/data/logs/aarch64/build.log https://kojipkgs.fedoraproject.org//packages/valgrind/3.23.0/4.fc41/data/logs/aarch64/build.log https://kojipkgs.fedoraproject.org//packages/valgrind/3.23.0/4.eln141/data/logs/aarch64/build.log It doesn't seem to consistently fail though. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 439082] memcheck/tests/linux/stack_changes fails on qemuarm64 builds
https://bugs.kde.org/show_bug.cgi?id=439082 Paul Floyd changed: What|Removed |Added CC||[email protected] --- Comment #4 from Paul Floyd --- Do you still have this problem? If so could you attach the unfiltered log file? Run perl tests/vg_regtest --keep-unfiltered memcheck/tests/linux/stack_changes and then attach stack_changes.stderr.out.unfiltered.out I'll try it on FreeBSD - reading the commit comments, it's only Darwin that doesn't work with this test. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 439082] memcheck/tests/linux/stack_changes fails on qemuarm64 builds
https://bugs.kde.org/show_bug.cgi?id=439082 --- Comment #3 from Tony Tascioglu --- This works fine on x86_64, and it works when compiled on a Raspberry Pi, but when cross-compiled with Yocto and run on qemuarm64 (on an x86_64 build host), it fails close to 100% of the time. Is there something we can do to help gather more information to help debug this or make progress on the bug? Thanks, Tony -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 439082] memcheck/tests/linux/stack_changes fails on qemuarm64 builds
https://bugs.kde.org/show_bug.cgi?id=439082 --- Comment #2 from Tony Tascioglu --- Created attachment 139623 --> https://bugs.kde.org/attachment.cgi?id=139623&action=edit expected vs actual test result from stderr -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 439082] memcheck/tests/linux/stack_changes fails on qemuarm64 builds
https://bugs.kde.org/show_bug.cgi?id=439082 --- Comment #1 from Tony Tascioglu --- My apologies, that log is from an older testing attempt that was run without the --valgrind and --valgrind-lib parameters. When run correctly as follows, the test fails with the incorrect diff seen during testing. root@qemuarm64:/usr/lib/valgrind/ptest# ./tests/vg_regtest --valgrind=/usr/bin/valgrind --valgrind-lib=/usr/libexec/valgrind memcheck/tests/linux/stack_changes stack_changes: valgrind -q ./stack_changes *** stack_changes failed (stderr) *** == 1 test, 1 stderr failure, 0 stdout failures, 0 stderrB failures, 0 stdoutB failures, 0 post failures == memcheck/tests/linux/stack_changes (stderr) I have attached the stderr diff between the expected output and the result from the test that causes the failure. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 439082] memcheck/tests/linux/stack_changes fails on qemuarm64 builds
https://bugs.kde.org/show_bug.cgi?id=439082 Randy MacLeod changed: What|Removed |Added CC||[email protected] -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 439082] memcheck/tests/linux/stack_changes fails on qemuarm64 builds
https://bugs.kde.org/show_bug.cgi?id=439082 Tony Tascioglu changed: What|Removed |Added CC||[email protected] ||m -- You are receiving this mail because: You are watching all bug changes.
