Printf is not working in C signal handler

by

In short: you cannot safely use printf within a signal handler.

There’s a list of authorized functions in signal handler’s man page. There is not fprintf in it.

That’s because this function is not reentrant, mainly because it can use malloc and free.
See this post for a detailed explanation.

More Related Contents:

  1. How to Raise SIGTERM in Windows [closed]
  2. Capturing signals in C
  3. How to avoid using printf in a signal handler?
  4. What is the difference between sigaction and signal?
  5. How to prevent SIGPIPEs (or handle them properly)
  6. Catch Ctrl-C in C
  7. How to capture Control+D signal?
  8. POSIX threads and signals
  9. Segmentation fault handling
  10. What does fflush(stdin) do in C programing? [duplicate]
  11. Signal handling with multiple threads in Linux
  12. How does sig_atomic_t actually work?
  13. Signal handling in pthreads
  14. Simple Signals – C programming and alarm function
  15. Print int from signal handler using write or async-safe functions
  16. Does linux allow any system call to be made from signal handlers?
  17. Providing/passing argument to signal handler
  18. Which thread handles the signal?
  19. Signal queuing in C
  20. Checking if errno != EINTR: what does it mean?
  21. Linux: Why is sig_atomic_t typedef’ed to int?
  22. executing default signal handler
  23. How do I get tcsetpgrp() to work in C?
  24. Oracle Pro*C/OCI install handlers for SIGSEGV/SIGABRT and friends – why, and how to disable?
  25. longjmp() from signal handler
  26. Debugging child process after fork (follow-fork-mode child configured)
  27. Why can’t I ignore SIGSEGV signal?
  28. i get Error while trying to compile and Run, [Linker error] undefined reference to `scand’ [closed]
  29. C – Serialization of the floating point numbers (floats, doubles)
  30. What can cause a “Resource temporarily unavailable” on sock send() command

Leave a Comment