run_command: handle better debug output

Without that we have the commands output that are printed as-is
without any way to understand where these prints come from.

Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>

1 files changed, 5 insertions, 1 deletions

diff --git a/tests.c b/tests.c
index 955d8f3..a5990bd 100644
--- a/tests.c
+++ b/tests.c
@@ -37,7 +37,11 @@ static int run_command(int debug, char *command)
 	int rc;
 
 	if (debug) {
-		return system(command);
+		printf("%s: running \"%s\"\n", __func__, command);
+		rc = system(command);
+		printf("%s: %s exited with result %d\n", __func__, command, rc);
+
+		return rc;
 	} else {
 		rc = asprintf(&silent_command, "%s 1>/dev/null", command);
 		if (rc == -1) {