Segmentation fault handling

by

The default action for things like SIGSEGV is to terminate your process but as you’ve installed a handler for it, it’ll call your handler overriding the default behavior. But the problem is segfaulting instruction may be retried after your handler finishes and if you haven’t taken measures to fix the first seg fault, the retried instruction will again fault and it goes on and on.

So first spot the instruction that resulted in SIGSEGV and try to fix it (you can call something like backtrace() in the handler and see for yourself what went wrong)

Also, the POSIX standard says that,

The behavior of a process is undefined after it returns normally from
a signal-catching function for a [XSI] SIGBUS, SIGFPE, SIGILL, or
SIGSEGV signal that was not generated by kill(), [RTS] sigqueue(),
or raise().

So, the ideal thing to do is to fix your segfault in the first place. Handler for segfault is not meant to bypass the underlying error condition

So the best suggestion would be- Don’t catch the SIGSEGV. Let it dump core. Analyze the core. Fix the invalid memory reference and there you go!

More Related Contents:

  1. How to avoid using printf in a signal handler?
  2. How to write a signal handler to catch SIGSEGV?
  3. How to capture Control+D signal?
  4. Signal handling with multiple threads in Linux
  5. How does sig_atomic_t actually work?
  6. Does linux allow any system call to be made from signal handlers?
  7. Providing/passing argument to signal handler
  8. Which thread handles the signal?
  9. Signal queuing in C
  10. Checking if errno != EINTR: what does it mean?
  11. Linux: Why is sig_atomic_t typedef’ed to int?
  12. executing default signal handler
  13. What is the octet mode in TFTP?
  14. C – list all files in current directory then move in directory above, list files, and so on until root directory is reached [closed]
  15. How to prevent SIGPIPEs (or handle them properly)
  16. Can I share a file descriptor to another process on linux or are they local to the process?
  17. How to list files in a directory in a C program?
  18. Get IP address of an interface on Linux
  19. What does fflush(stdin) do in C programing? [duplicate]
  20. What is the purpose of a these #define within an enum?
  21. How to implement a timeout in read() function call?
  22. Increasing limit of FD_SETSIZE and select
  23. How do I get a thread ID from an arbitrary pthread_t?
  24. how could I intercept linux sys calls?
  25. Why am I able to perform floating point operations inside a Linux kernel module?
  26. Why getch() returns before press any key?
  27. Do threads have a distinct heap?
  28. Implicit declaration of ‘gets’
  29. Implementing pipe in C
  30. How to print exact value of the program counter in C

Leave a Comment