Avoid calling close(-1)

While this is perfectly OK on Unix, it causes annoying valgrind
warnings, and might be otherwise confusing to others.

On Windows, the runtime can actually abort the process if this is
called.

push.c part taken from a patch by Pedro Pombeiro.

1 files changed, 4 insertions, 2 deletions

diff --git a/input/ipc-unix.c b/input/ipc-unix.c
index f26e0cadde..c3315d21b5 100644
--- a/input/ipc-unix.c
+++ b/input/ipc-unix.c
@@ -402,8 +402,10 @@ struct mp_ipc_ctx *mp_init_ipc(struct mp_client_api *client_api,
     return arg;
 
 out:
-    close(arg->death_pipe[0]);
-    close(arg->death_pipe[1]);
+    if (arg->death_pipe[0] >= 0) {
+        close(arg->death_pipe[0]);
+        close(arg->death_pipe[1]);
+    }
     talloc_free(arg);
     return NULL;
 }