libzmq: Problem: UDP engine aborts on networking-related errors from socket syscalls
Description
I have a dish socket bind to a multicast address. And dish socket receiving messages in a while loop.
It works fine when there is an Ethernet interface is up.
I did sudo ifconfig enp7s0 0.0.0.0 and observed the following:
No such device (src/udp_engine.cpp:142)
Aborted (core dumped)
I am using this dish socket in an application in which the ip address of the interface often becomes 0.0.0.0.
Is there any way I could exit the while loop safely without core dumping the entire application?
Environment
- Version: Zeromq 4.2.1
- OS: Ubuntu 16.04
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Comments: 15 (11 by maintainers)
Commits related to this issue
- UDP engine aborts on networking-related errors from socket syscalls #2862 — committed to atomashpolskiy/libzmq by atomashpolskiy 5 years ago
- UDP engine aborts on networking-related errors from socket syscalls #2862 — committed to atomashpolskiy/libzmq by atomashpolskiy 5 years ago
- UDP engine aborts on networking-related errors from socket syscalls #2862 (fix) — committed to atomashpolskiy/libzmq by atomashpolskiy 5 years ago
- UDP engine aborts on networking-related errors from socket syscalls #2862 (clang-format) — committed to atomashpolskiy/libzmq by atomashpolskiy 5 years ago
- UDP engine aborts on networking-related errors from socket syscalls #2862 (remove unused function) — committed to atomashpolskiy/libzmq by atomashpolskiy 5 years ago
- UDP engine aborts on networking-related errors from socket syscalls #2862 (format) — committed to atomashpolskiy/libzmq by atomashpolskiy 5 years ago
- UDP engine aborts on networking-related errors from socket syscalls #2862 (#3638) * UDP engine aborts on networking-related errors from socket syscalls #2862 * Add relicense statement — committed to zeromq/libzmq by atomashpolskiy 5 years ago
- UDP engine aborts on networking-related errors from socket syscalls #2862 — committed to atomashpolskiy/libzmq by atomashpolskiy 5 years ago
- UDP engine aborts on networking-related errors from socket syscalls #2862 — committed to atomashpolskiy/libzmq by atomashpolskiy 5 years ago
- UDP engine aborts on networking-related errors from socket syscalls #2862 (fix) — committed to atomashpolskiy/libzmq by atomashpolskiy 5 years ago
- UDP engine aborts on networking-related errors from socket syscalls #2862 (fix) — committed to atomashpolskiy/libzmq by atomashpolskiy 5 years ago
- UDP engine aborts on networking-related errors from socket syscalls #2862 (revert changes in error list in zmq::assert_success_or_recoverable) — committed to atomashpolskiy/libzmq by atomashpolskiy 5 years ago
- UDP engine aborts on networking-related errors from socket syscalls (2) #2862 (#3640) * UDP engine aborts on networking-related errors from socket syscalls #2862 — committed to zeromq/libzmq by atomashpolskiy 5 years ago
Great, happy you found a workaround and thanks for sharing it.
I’ll reopen and retitle the issue, as the UDP implementation should be hardened anyway before it can be declared stable.