sm_io/sm_io.c: fix wrong PIPE destruction on SMIO exit

This causes an assertion error as the zactor infrastructure needs the PIPE after the thread exits. This fixes #116 github issue.

sm_io/sm_io.c: fix wrong PIPE destruction on SMIO exit
This causes an assertion error as the zactor infrastructure needs the PIPE after the thread exits. This fixes #116 github issue.
4469b2e9 · Lucas Russo · 51b90980 · 4469b2e9
Commit 4469b2e9 authored Apr 20, 2016 by Lucas Russo
Hide whitespace changes
Inline Side-by-side

Showing with 5 additions and 1 deletion

sm_io.c src/sm_io/sm_io.c +5 -1

No files found.
--- a/src/sm_io/sm_io.c
+++ b/src/sm_io/sm_io.c
@@ -176,7 +176,11 @@ smio_err_e smio_destroy (smio_t **self_p)
        zsock_destroy (&self->pipe_backend);
        zsock_destroy (&self->pipe_frontend);
        zsock_destroy (&self->pipe_msg);
-        zsock_destroy (&self->pipe_mgmt);
+        /* Don't destroy pipe_mgmt as this is taken care of by the
+         * zactor infrastructure, s_thread_shim (void *args) on CZMQ 
+         * 3.0.2 src/zactor.c 
+         * zsock_destroy (&self->pipe_mgmt);
+         */
        disp_table_destroy (&self->exp_ops_dtable);
        self->thsafe_client_ops = NULL;
        self->ops = NULL;