Providing/passing argument to signal handler

by

You can’t have data of your own passed to the signal handler as parameters. Instead you’ll have to store your parameters in global variables. (And be really, really careful if you ever need to change those data after installing the the signal handler).

Response to edit 0: Historical reasons. Signals are a really old and really low-level design. Basically you’re just given the kernel a single address to some machine code and asking it to go to this specific address if such and such happens. We’re back in the “portable assembler” mindset here, where the kernels provide a no-frills baseline service, and whatever the user process can reasonably be expected to to for itself, it must do itself.

Also, the usual arguments against global variables don’t really apply here. The signal handler itself is a global setting, so there is no relevant possibility of having several different sets of user-specified parameters for it around. (Well, actually it is not entirely global but only thread-global. But the threading API will include some mechanism for thread-local storage, which is just what you need in this case).

More Related Contents:

  1. Segmentation fault handling
  2. How to Raise SIGTERM in Windows [closed]
  3. Capturing signals in C
  4. How to avoid using printf in a signal handler?
  5. What is the difference between sigaction and signal?
  6. How to prevent SIGPIPEs (or handle them properly)
  7. How to write a signal handler to catch SIGSEGV?
  8. Catch Ctrl-C in C
  9. How to capture Control+D signal?
  10. POSIX threads and signals
  11. What does fflush(stdin) do in C programing? [duplicate]
  12. Signal handling with multiple threads in Linux
  13. Printf is not working in C signal handler
  14. How does sig_atomic_t actually work?
  15. Signal handling in pthreads
  16. Simple Signals – C programming and alarm function
  17. Print int from signal handler using write or async-safe functions
  18. Does linux allow any system call to be made from signal handlers?
  19. Which thread handles the signal?
  20. Signal queuing in C
  21. Checking if errno != EINTR: what does it mean?
  22. Linux: Why is sig_atomic_t typedef’ed to int?
  23. executing default signal handler
  24. How do I get tcsetpgrp() to work in C?
  25. Oracle Pro*C/OCI install handlers for SIGSEGV/SIGABRT and friends – why, and how to disable?
  26. longjmp() from signal handler
  27. Debugging child process after fork (follow-fork-mode child configured)
  28. Why can’t I ignore SIGSEGV signal?
  29. Can I get Unix’s pthread.h to compile in Windows?
  30. C – initialization of pointers, asterisk position [duplicate]

Leave a Comment