diff options
| author | Michael Hudson-Doyle <michael.hudson@canonical.com> | 2020-03-11 13:05:25 +1300 |
|---|---|---|
| committer | DJ Delorie <dj@redhat.com> | 2020-03-11 16:00:58 -0400 |
| commit | 083d644d420f49c992667f4c7a54848ad3dee54d (patch) | |
| tree | bf66a285b7d22c61cfdbd96bf5a151a090e17f30 | |
| parent | 700065132744e0dfa6d4d9142d63f6e3a1934726 (diff) | |
| download | glibc-083d644d420f49c992667f4c7a54848ad3dee54d.tar.gz glibc-083d644d420f49c992667f4c7a54848ad3dee54d.tar.xz glibc-083d644d420f49c992667f4c7a54848ad3dee54d.zip | |
test-container: print errno when execvp fails
I'm debugging a situation where lots of tests using test-container fail and it's possible knowing errno would help understand why. Reviewed-by: DJ Delorie <dj@redhat.com>
| -rw-r--r-- | support/test-container.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/support/test-container.c b/support/test-container.c index e970eb2c18..dff2ff379e 100644 --- a/support/test-container.c +++ b/support/test-container.c @@ -1145,7 +1145,7 @@ main (int argc, char **argv) execvp (new_child_exec, new_child_proc); /* Or don't run the child? */ - FAIL_EXIT1 ("Unable to exec %s\n", new_child_exec); + FAIL_EXIT1 ("Unable to exec %s: %s\n", new_child_exec, strerror (errno)); /* Because gcc won't know error () never returns... */ exit (EXIT_UNSUPPORTED); |