public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug libc/31129] New: elf/tst-stackguard1-static and ntpl/tst-stackguard1-static failing on sparc64-linux-gnu
@ 2023-12-09 21:43 glaubitz at physik dot fu-berlin.de
2024-01-17 12:48 ` [Bug libc/31129] " adhemerval.zanella at linaro dot org
` (3 more replies)
0 siblings, 4 replies; 5+ messages in thread
From: glaubitz at physik dot fu-berlin.de @ 2023-12-09 21:43 UTC (permalink / raw)
To: glibc-bugs
https://sourceware.org/bugzilla/show_bug.cgi?id=31129
Bug ID: 31129
Summary: elf/tst-stackguard1-static and
ntpl/tst-stackguard1-static failing on
sparc64-linux-gnu
Product: glibc
Version: 2.38
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: libc
Assignee: unassigned at sourceware dot org
Reporter: glaubitz at physik dot fu-berlin.de
CC: adhemerval.zanella at linaro dot org, drepper.fsp at gmail dot com,
matorola at gmail dot com, sam at gentoo dot org
Target Milestone: ---
Target: sparc64-linux-gnu
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
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 5+ messages in thread
* [Bug libc/31129] elf/tst-stackguard1-static and ntpl/tst-stackguard1-static failing on sparc64-linux-gnu
2023-12-09 21:43 [Bug libc/31129] New: elf/tst-stackguard1-static and ntpl/tst-stackguard1-static failing on sparc64-linux-gnu glaubitz at physik dot fu-berlin.de
@ 2024-01-17 12:48 ` adhemerval.zanella at linaro dot org
2024-02-21 11:39 ` glaubitz at physik dot fu-berlin.de
` (2 subsequent siblings)
3 siblings, 0 replies; 5+ messages in thread
From: adhemerval.zanella at linaro dot org @ 2024-01-17 12:48 UTC (permalink / raw)
To: glibc-bugs
https://sourceware.org/bugzilla/show_bug.cgi?id=31129
--- Comment #1 from Adhemerval Zanella <adhemerval.zanella at linaro dot org> ---
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?
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 5+ messages in thread
* [Bug libc/31129] elf/tst-stackguard1-static and ntpl/tst-stackguard1-static failing on sparc64-linux-gnu
2023-12-09 21:43 [Bug libc/31129] New: elf/tst-stackguard1-static and ntpl/tst-stackguard1-static failing on sparc64-linux-gnu glaubitz at physik dot fu-berlin.de
2024-01-17 12:48 ` [Bug libc/31129] " adhemerval.zanella at linaro dot org
@ 2024-02-21 11:39 ` glaubitz at physik dot fu-berlin.de
2024-02-21 19:14 ` adhemerval.zanella at linaro dot org
2024-02-22 15:12 ` glaubitz at physik dot fu-berlin.de
3 siblings, 0 replies; 5+ messages in thread
From: glaubitz at physik dot fu-berlin.de @ 2024-02-21 11:39 UTC (permalink / raw)
To: glibc-bugs
https://sourceware.org/bugzilla/show_bug.cgi?id=31129
--- Comment #2 from John Paul Adrian Glaubitz <glaubitz at physik dot fu-berlin.de> ---
(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.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 5+ messages in thread
* [Bug libc/31129] elf/tst-stackguard1-static and ntpl/tst-stackguard1-static failing on sparc64-linux-gnu
2023-12-09 21:43 [Bug libc/31129] New: elf/tst-stackguard1-static and ntpl/tst-stackguard1-static failing on sparc64-linux-gnu glaubitz at physik dot fu-berlin.de
2024-01-17 12:48 ` [Bug libc/31129] " adhemerval.zanella at linaro dot org
2024-02-21 11:39 ` glaubitz at physik dot fu-berlin.de
@ 2024-02-21 19:14 ` adhemerval.zanella at linaro dot org
2024-02-22 15:12 ` glaubitz at physik dot fu-berlin.de
3 siblings, 0 replies; 5+ messages in thread
From: adhemerval.zanella at linaro dot org @ 2024-02-21 19:14 UTC (permalink / raw)
To: glibc-bugs
https://sourceware.org/bugzilla/show_bug.cgi?id=31129
--- Comment #3 from Adhemerval Zanella <adhemerval.zanella at linaro dot org> ---
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"
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 5+ messages in thread
* [Bug libc/31129] elf/tst-stackguard1-static and ntpl/tst-stackguard1-static failing on sparc64-linux-gnu
2023-12-09 21:43 [Bug libc/31129] New: elf/tst-stackguard1-static and ntpl/tst-stackguard1-static failing on sparc64-linux-gnu glaubitz at physik dot fu-berlin.de
` (2 preceding siblings ...)
2024-02-21 19:14 ` adhemerval.zanella at linaro dot org
@ 2024-02-22 15:12 ` glaubitz at physik dot fu-berlin.de
3 siblings, 0 replies; 5+ messages in thread
From: glaubitz at physik dot fu-berlin.de @ 2024-02-22 15:12 UTC (permalink / raw)
To: glibc-bugs
https://sourceware.org/bugzilla/show_bug.cgi?id=31129
--- Comment #4 from John Paul Adrian Glaubitz <glaubitz at physik dot fu-berlin.de> ---
Created attachment 15376
--> https://sourceware.org/bugzilla/attachment.cgi?id=15376&action=edit
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.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2024-02-22 15:12 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-12-09 21:43 [Bug libc/31129] New: elf/tst-stackguard1-static and ntpl/tst-stackguard1-static failing on sparc64-linux-gnu glaubitz at physik dot fu-berlin.de
2024-01-17 12:48 ` [Bug libc/31129] " adhemerval.zanella at linaro dot org
2024-02-21 11:39 ` glaubitz at physik dot fu-berlin.de
2024-02-21 19:14 ` adhemerval.zanella at linaro dot org
2024-02-22 15:12 ` glaubitz at physik dot fu-berlin.de
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).