Simon Giesecke

I transferred this issue to zeromq/libzmq. cppzmq only passes through the values generated by libzmq.

Never mind :) The separation between cppzmq and libzmq is not obvious in all aspects.

NB: In https://github.com/sigiesec/libzmq/tree/test-coverage-arm64, I added a job doing this, which works fine in terms of the coverage report: https://coveralls.io/builds/33254295 (coveralls automatically merges the two coverage reports for the same revision)....

As it says, `ZMQ_RADIO`/`ZMQ_DISH` works, unless you `zmq_setsockopt` `ZMQ_MULTICAST_LOOP` to `false/0`. I don't know if that's relevant for you? I am not sure if ZMQ_MULTICAST_LOOP can even be set to...

From this code fragment, it's hard to tell what's going wrong. Can you give us a more complete example, including how the context and socket are created? Which error code...

I wonder why it looks as if all job definitions were changed in .travis.yml... Maybe the indentation changed or so, I will try to get that fixed.

#4120 now added a non-coverage ARM64 job, so this PR should be changed to just make that into a coverage job.

Please provide a minimal example that reproduces the problem. Your assumption that it is necessary to unbind sockets is not correct. However, you need to close all sockets. Context termination...

Since cppzmq is a header-only library, you do not need to build it, you can just copy the header files.

I am not sure if I understand the problem here completely. Shutting down monitoring right is rather tricky, unfortunately. I am currently investigating an issue in libzmq related to that...