From: Florian Weimer <fweimer@redhat.com>
To: Joe Simmons-Talbott via Libc-help <libc-help@sourceware.org>
Cc: Joe Simmons-Talbott <joetalbott@gmail.com>
Subject: Re: Testcase for BZ 28519
Date: Mon, 20 Mar 2023 21:14:51 +0100 [thread overview]
Message-ID: <87cz53rxhg.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <20230320180132.GA1698111@oak> (Joe Simmons-Talbott via Libc-help's message of "Mon, 20 Mar 2023 14:10:21 -0400")
* Joe Simmons-Talbott via Libc-help:
> Hi,
>
> I'm trying to write a testcase for BZ 28519 but not having much luck.
> My testcase is below. For a simple application that calls
> 'system("-echo")' I get the same behavior as the BZ but for the testcase
> I get the expected behavior where sh fails to find "-echo".
>
> Does anyone have any thought on what I might be missing?
I suspect it's because of
tests-container := \
tst-system \
#tests-container
in stdlib/Makefile. /bin/sh in the container is not a real /bin/sh,
so it has different behavior.
Thanks,
Florian
next prev parent reply other threads:[~2023-03-20 20:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-20 18:10 Joe Simmons-Talbott
2023-03-20 20:14 ` Florian Weimer [this message]
2023-03-21 17:19 ` Joe Talbott
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=87cz53rxhg.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=joetalbott@gmail.com \
--cc=libc-help@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).