Re: [zeromq-dev] Using libsdp and zeromq

[Michael Rissi]

 Being clever in zeromq and unsetting HAVE_SOCK_CLOEXEC will not help, as
the
 zeromq server will
 crash sooner or later when exiting a client.


Nothing will crash. It will leak socket if you will run exec call or
fork then exec. Which is usually avoidable in zeromq apps. To remove
memory leak you can use one of the techniques, described here:


http://stackoverflow.com/questions/899038/getting-the-highest-allocated-file-descriptor

Dear Paul,
Thanks for the quick answer! Unfortunately, the zeromq server does crash,
with a thrown error:

Invalid argument (stream_engine.cpp:323).
Aborted (core dumped)

or with this error:
Assertion failed: !more (lb.cpp:95)
Aborted (core dumped)


I use a simple push server, and a pull client.
What I did is commenting out
//#define ZMQ_HAVE_SOCK_CLOEXEC 1
in platform.hpp, compile, start the server and the client, and kill the
client (with ctrl c). There is no
fork or exec in my code.

Best regards,
Michael
___
zeromq-dev mailing list
zeromq-dev@lists.zeromq.org
http://lists.zeromq.org/mailman/listinfo/zeromq-dev

[zeromq-dev] Using libsdp and zeromq

[Michael Rissi]

Hello zeromq devs!

I tried to use zeromq with preloaded libsdp over infiniband. This
unfortunately fails. The reason for it is the
SOCK_CLOEXEC flag set in ip.cpp. Libsdp checks the socket type to be
exactly SOCK_STREAM. If
it is not the case (as in zeromq, where the socket type is type =
SOCK_STREAM | SOCK_CLOEXEC),
it will fall back to use TCP/IP. This can be found in line 681 of port.c in
the libsdp library (download under
http://www.openfabrics.org/downloads/libsdp/ )

Being clever in zeromq and unsetting HAVE_SOCK_CLOEXEC will not help, as
the zeromq server will
crash sooner or later when exiting a client.

Does anyone know if there is a solution to this problem?

Thanks a lot for your help!

Best regards,
Michael
___
zeromq-dev mailing list
zeromq-dev@lists.zeromq.org
http://lists.zeromq.org/mailman/listinfo/zeromq-dev