Print int from signal handler using write or async-safe functions

by

If you really insist on doing the printing from a signal handler, you basically have 2 options:

  1. Block the signal except in a dedicated thread you create for handling the signal. This special thread can simply perform for (;;) pause(); and since pause is async-signal-safe, the signal handler is allowed to use any functions it wants; it’s not restricted to only async-signal-safe functions. On the other hand, it does have to access shared resources in a thread-safe way, since you’re now dealing with threads.

  2. Write your own code for converting integers to decimal strings. It’s just a simple loop of using %10 and /10 to peel off the last digit and storing them to a short array.

However, I would highly recommend getting this operation out of the signal handler, using the self-pipe trick or similar.

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. Printf is not working in C signal handler
  13. How does sig_atomic_t actually work?
  14. Signal handling in pthreads
  15. Simple Signals – C programming and alarm function
  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. Printing UTF-8 strings with printf – wide vs. multibyte string literals
  29. Practical usage of setjmp and longjmp in C
  30. Modify a string with pointer [duplicate]

Leave a Comment