How to prevent SIGPIPEs (or handle them properly)

by

You generally want to ignore the SIGPIPE and handle the error directly in your code. This is because signal handlers in C have many restrictions on what they can do.

The most portable way to do this is to set the SIGPIPE handler to SIG_IGN. This will prevent any socket or pipe write from causing a SIGPIPE signal.

To ignore the SIGPIPE signal, use the following code:

signal(SIGPIPE, SIG_IGN);

If you’re using the send() call, another option is to use the MSG_NOSIGNAL option, which will turn the SIGPIPE behavior off on a per call basis. Note that not all operating systems support the MSG_NOSIGNAL flag.

Lastly, you may also want to consider the SO_SIGNOPIPE socket flag that can be set with setsockopt() on some operating systems. This will prevent SIGPIPE from being caused by writes just to the sockets it is set on.

More Related Contents:

  1. how to enter a function to a file in c
  2. How to Raise SIGTERM in Windows [closed]
  3. Capturing signals in C
  4. How to avoid using printf in a signal handler?
  5. How do you determine the size of a file in C?
  6. What is the difference between sigaction and signal?
  7. Catch Ctrl-C in C
  8. How to capture Control+D signal?
  9. POSIX threads and signals
  10. What causes the Broken Pipe Error?
  11. Difference between fprintf, printf and sprintf?
  12. Read from file or stdin
  13. How does sig_atomic_t actually work?
  14. What is the difference between getch() and getchar()?
  15. Signal handling in pthreads
  16. Simple Signals – C programming and alarm function
  17. plain C: opening a directory with fopen()
  18. Print int from signal handler using write or async-safe functions
  19. Providing/passing argument to signal handler
  20. Which thread handles the signal?
  21. Signal queuing in C
  22. Checking if errno != EINTR: what does it mean?
  23. Reading a file character by character in C
  24. Linux: Why is sig_atomic_t typedef’ed to int?
  25. executing default signal handler
  26. How do I get tcsetpgrp() to work in C?
  27. Return value of fgets()
  28. longjmp() from signal handler
  29. Debugging child process after fork (follow-fork-mode child configured)
  30. Why can’t I ignore SIGSEGV signal?

Leave a Comment