public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "adhemerval.zanella at linaro dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/31129] elf/tst-stackguard1-static and ntpl/tst-stackguard1-static failing on sparc64-linux-gnu
Date: Wed, 21 Feb 2024 19:14:01 +0000	[thread overview]
Message-ID: <bug-31129-131-z9Hu595hJK@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31129-131@http.sourceware.org/bugzilla/>

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.

  parent reply	other threads:[~2024-02-21 19:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-09 21:43 [Bug libc/31129] New: " 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 [this message]
2024-02-22 15:12 ` glaubitz at physik dot fu-berlin.de

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-31129-131-z9Hu595hJK@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).