public inbox for cygwin-cvs@sourceware.org help / color / mirror / Atom feed
From: Jon Turney <jturney@sourceware.org> To: cygwin-cvs@sourceware.org Subject: [newlib-cygwin] Cygwin: testsuite: also check direct call in systemcall Date: Sun, 9 Jul 2023 16:01:49 +0000 (GMT) [thread overview] Message-ID: <20230709160149.C18F73858438@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=f5940dc449177a3b6216515855964b0c8815954f commit f5940dc449177a3b6216515855964b0c8815954f Author: Jon Turney <jon.turney@dronecode.org.uk> Date: Sun Jul 9 12:12:23 2023 +0100 Cygwin: testsuite: also check direct call in systemcall Check direct call to system(), as well as one in a subprocess. (This is a lot easier to debug when it's completely broken by environment) Diff: --- winsup/testsuite/winsup.api/systemcall.c | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/winsup/testsuite/winsup.api/systemcall.c b/winsup/testsuite/winsup.api/systemcall.c index d10c9825c..a47586fdb 100644 --- a/winsup/testsuite/winsup.api/systemcall.c +++ b/winsup/testsuite/winsup.api/systemcall.c @@ -26,6 +26,14 @@ main (int argc, char **argv) fprintf (stderr, "couldn't redirect stdout to /dev/null, fd %d - %s\n", fd, strerror (errno)); exit (1); } + + n = system ("ls"); + if (n != 0) + { + fprintf (stderr, "system() call returned %x\n", n); + exit (1); + } + if (pipe (fds)) { fprintf (stderr, "pipe call failed - %s\n", strerror (errno)); @@ -61,7 +69,7 @@ main (int argc, char **argv) } if (n != 0) { - fprintf (stderr, "system() call returned %x\n", n); + fprintf (stderr, "system() call in child process returned %x\n", n); exit (1); } exit (0);
next reply other threads:[~2023-07-09 16:01 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-07-09 16:01 Jon Turney [this message] 2023-07-14 15:28 [newlib-cygwin] Cygwin: testsuite: Also " Jon Turney
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=20230709160149.C18F73858438@sourceware.org \ --to=jturney@sourceware.org \ --cc=cygwin-cvs@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: linkBe 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).