run-command: be more informative about what failed
authorStephen Boyd <sboyd@codeaurora.org>
Thu, 31 Jan 2013 02:01:05 +0000 (18:01 -0800)
committerJunio C Hamano <gitster@pobox.com>
Fri, 1 Feb 2013 22:11:50 +0000 (14:11 -0800)
commit939296c4a42b0eb22542f0fe2e50b53993489eff
treea731680c80eeaefec27ecced14aa133fc64aa56f
parent7e2010537e96d0a1144520222f20ba1dc3d61441
run-command: be more informative about what failed

While debugging an error with verify_signed_buffer() the error
messages from run-command weren't very useful:

 error: cannot create pipe for gpg: Too many open files
 error: could not run gpg.

because they didn't indicate *which* pipe couldn't be created.

Print which pipe failed to be created in the error message so we
can more easily debug similar problems in the future.

For example, the above error now prints:

 error: cannot create standard error pipe for gpg: Too many open files
 error: could not run gpg.

Signed-off-by: Stephen Boyd <sboyd@codeaurora.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
run-command.c