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 dynamic-link/29187] New: [regression] broken argv adjustment for nios2
Date: Thu, 26 May 2022 16:33:45 +0000	[thread overview]
Message-ID: <bug-29187-131@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=29187

            Bug ID: 29187
           Summary: [regression] broken argv adjustment for nios2
           Product: glibc
           Version: 2.36
            Status: NEW
          Severity: normal
          Priority: P2
         Component: dynamic-link
          Assignee: unassigned at sourceware dot org
          Reporter: adhemerval.zanella at linaro dot org
  Target Milestone: ---

With ad43cac44a6860eaefcadadfb2acb349921e96bf:

$ cat test.c
#include <stdio.h>

int main (int argc, char *argv[])
{
  for (int i = 0; i < argc; i++)
    printf ("argv[%d]=%s\n", i, argv[i]);
  return 0;
}
$ qemu-nios2 elf/ld.so --library-path . ./test 1 2 3 4
argv[0]=./test
argv[1]=1
argv[2]=2
argv[3]=3
argv[4]=4


With 86147bbeec25624cb26bb7646cdbc3a49bc56bf5 (rtld: Remove DL_ARGV_NOT_RELRO
and make _dl_skip_args const):

$ qemu-nios2 elf/ld.so --library-path . ./test 1 2 3 4
qemu: uncaught target signal 11 (Segmentation fault) - core dumped
Segmentation fault (core dumped)

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2022-05-26 16:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-26 16:33 adhemerval.zanella at linaro dot org [this message]
2022-05-30 20:49 ` [Bug dynamic-link/29187] " adhemerval.zanella at linaro dot org

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-29187-131@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).