take care of SIGPIPE received when writing a dead socket
write() on a socket with the other end closed throws a SIGPIPE. Let's ignore this signal. write() will return an error anyway...
Showing
- common/utils/T/local_tracer.c 5 additions, 0 deletionscommon/utils/T/local_tracer.c
- common/utils/T/tracer/enb.c 4 additions, 0 deletionscommon/utils/T/tracer/enb.c
- common/utils/T/tracer/textlog.c 4 additions, 0 deletionscommon/utils/T/tracer/textlog.c
- common/utils/T/tracer/vcd.c 4 additions, 0 deletionscommon/utils/T/tracer/vcd.c
Loading
Please register or sign in to comment