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/28499] Couldn't export variable to sub process
Date: Tue, 26 Oct 2021 20:15:12 +0000 [thread overview]
Message-ID: <bug-28499-131-LYygXENeWX@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28499-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=28499
Adhemerval Zanella <adhemerval.zanella at linaro dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
Ever confirmed|0 |1
CC| |adhemerval.zanella at linaro dot o
| |rg
Last reconfirmed| |2021-10-26
--- Comment #1 from Adhemerval Zanella <adhemerval.zanella at linaro dot org> ---
At least with bash and dash I could not reproduce it:
$ ./elf/ld.so --version | head -n1
ld.so (GNU libc) development release version 2.34.9000.
$ ./elf/ld.so --library-path . /bin/bash ./export.sh
5
5
$ ./elf/ld.so --library-path . /bin/dash ./export.sh
5
5
And on both shells they call fork+exec and we do have tests that rely on forked
process to retains the environment variables (posix/tst-execvpe5.c). I will
close this bug by the end of the week.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-10-26 20:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-26 14:40 [Bug libc/28499] New: " drvignesh1992 at gmail dot com
2021-10-26 20:15 ` adhemerval.zanella at linaro dot org [this message]
2021-10-27 13:40 ` [Bug libc/28499] " drvignesh1992 at gmail dot com
2021-10-27 14:04 ` adhemerval.zanella at linaro dot org
2021-11-01 10:10 ` drvignesh1992 at gmail dot com
2021-11-01 12:01 ` adhemerval.zanella at linaro dot org
2021-11-02 10:48 ` drvignesh1992 at gmail dot com
2021-11-02 12:47 ` adhemerval.zanella at linaro dot org
2021-11-12 10:50 ` fweimer at redhat dot com
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-28499-131-LYygXENeWX@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).