On Debian unstable on sparc64 (sparc64-linux-gnu), the following two tests are failing: FAIL: elf/tst-stackguard1-static FAIL: nptl/tst-stackguard1-static Full build log in [1]. For 2.37, the two failures don't show but I'm not sure whether these are actually simply not tested for 2.37 [2]. > [1] https://buildd.debian.org/status/fetch.php?pkg=glibc&arch=sparc64&ver=2.38-4&stamp=1701668542&raw=0 > [2] https://buildd.debian.org/status/fetch.php?pkg=glibc&arch=sparc64&ver=2.37-13&stamp=1701640851&raw=0
I don't see these with my testing on a sparc64 machine from gentoo project. I don't use the system compilers, so I am not sure it is subject to any out-of-tree patch. Do you have any more information, like a debugger output, to narrow the issue?
(In reply to Adhemerval Zanella from comment #1) > I don't see these with my testing on a sparc64 machine from gentoo project. > I don't use the system compilers, so I am not sure it is subject to any > out-of-tree patch. Do you have any more information, like a debugger output, > to narrow the issue? Let me try to run the tests in gdb to obtain a backtrace.
Note: issuing elf/tst-stackguard1-static with an argument will hit an issue on how we define glibc test long options, where support/test-driver.c fails to append a final zero-filled element: diff --git a/support/test-driver.c b/support/test-driver.c index f0fd7ccda2..8cf06793b4 100644 --- a/support/test-driver.c +++ b/support/test-driver.c @@ -155,6 +155,7 @@ main (int argc, char **argv) { CMDLINE_OPTIONS TEST_DEFAULT_OPTIONS + { NULL, 0, NULL, 0 } }; test_config.options = &options; #endif Could you check with this argument as from the following command? $ make test t=elf/tst-stackguard1-static For instance, on the system I built with --enable-hardcoded-path-in-tests (no need to setup the GCONV_PATH/LOCPATH/LC_ALL environment for this test): $ gdb --args /home/azanella/projects/glibc/build/sparc64-linux-gnu/elf/tst-stackguard1-static --command "/home/azanella/projects/glibc/build/sparc64-linux-gnu/elf/tst-stackguard1-static --child"
Created attachment 15376 [details] Backtrace for tst-stackguard1-static Sending the backtrace as an attachment because it previously resulted in my account being banned due to a false positive detection from the spam filter.