dgram: append actual errors to ERR_SOCKET_CANNOT_SEND
One of our apps has used up all available ports because of misuse and we have noticed some ERR_SOCKET_CANNOT_SEND
errors in our logs indicating this. I think appending the actual errors to the ERR_SOCKET_CANNOT_SEND
error would help with diagnosing.
This commit appends the actual error to the emitted ERR_SOCKET_CANNOT_SEND
error so that we could know the detailed reason why the send()
operation
failed.
Checklist
-
make -j4 test
(UNIX), orvcbuild test
(Windows) passes -
tests and/or benchmarks are included -
commit message follows commit guidelines