diff options
| author | Trevor Gross <t.gross35@gmail.com> | 2024-07-27 13:32:57 -0400 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-07-27 13:32:57 -0400 |
| commit | 2b58d8c08c2b73325a60c8a5cd78381743ebaa0c (patch) | |
| tree | 99a725890c56e01dae638c35e4e65011110eee13 /compiler/rustc_codegen_llvm/src | |
| parent | ee25d992998cff9b067ce6a63ead16e7b3112bf7 (diff) | |
| parent | 50d127e6ecb83f267fe35321eb14e536b959bb1d (diff) | |
| download | rust-2b58d8c08c2b73325a60c8a5cd78381743ebaa0c.tar.gz rust-2b58d8c08c2b73325a60c8a5cd78381743ebaa0c.zip | |
Rollup merge of #128259 - sunshowers:msg-nosignal, r=Mark-Simulacrum
[illumos/solaris] set MSG_NOSIGNAL while writing to sockets Both these platforms have MSG_NOSIGNAL available, and we should set it for socket writes in the event that the SIGPIPE handler has been reset to SIG_DFL (i.e. terminate the process). I've verified via a quick program at https://github.com/sunshowers/msg-nosignal-test/ that even when the SIGPIPE handler is reset to SIG_DFL, writes to closed TCP sockets now error out with EPIPE. (Under ordinary circumstances UDP writes won't cause MSG_NOSIGNAL.) However, I couldn't find any existing tests which verified the MSG_NOSIGNAL behavior.
Diffstat (limited to 'compiler/rustc_codegen_llvm/src')
0 files changed, 0 insertions, 0 deletions