Why can’t I ignore SIGSEGV signal?

by

Your code is ignoring SIGSEGV instead of catching it. Recall that the instruction that triggered the signal is restarted after handling the signal. In your case, handling the signal didn’t change anything so the next time round the offending instruction is tried, it fails the same way.

If you intend to catch the signal change this

signal(SIGSEGV, SIG_IGN);

to this

signal(SIGSEGV, sighandler);

You should probably also use sigaction() instead of signal(). See relevant man pages.

In your case the offending instruction is the one which tries to dereference the NULL pointer.

printf("%d", *p);

What follows is entirely dependent on your platform.

You can use gdb to establish what particular assembly instruction triggers the signal. If your platform is anything like mine, you’ll find the instruction is

movl    (%rax), %esi

with rax register holding value 0, i.e. NULL. One (non-portable!) way to fix this in your signal handler is to use the third argument signal your handler gets, i.e. the user context. Here is an example:

#include <signal.h>
#include <stdio.h>

#define __USE_GNU
#include <ucontext.h>

int *p = NULL;
int n = 100;

void sighandler(int signo, siginfo_t *si, ucontext_t* context)
{
  printf("Handler executed for signal %d\n", signo);
  context->uc_mcontext.gregs[REG_RAX] = &n;
}

int main(int argc,char ** argv)
{
  signal(SIGSEGV, sighandler);
  printf("%d\n", *p); // ... movl (%rax), %esi ...
  return 0;
}

This program displays:

Handler executed for signal 11
100

It first causes the handler to be executed by attempting to dereference a NULL address. Then the handler fixes the issue by setting rax to the address of variable n. Once the handler returns the system retries the offending instruction and this time succeeds. printf() receives 100 as its second argument.

I strongly recommend against using such non-portable solutions in your programs, though.

More Related Contents:

  1. How to capture Control+D signal?
  2. longjmp() from signal handler
  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. stat() error ‘No such file or directory’ when file name is returned by readdir()
  7. What is a bus error? Is it different from a segmentation fault?
  8. C Minishell Adding Pipelines
  9. Segmentation fault handling
  10. Please explain the exec() function and its family
  11. Non-blocking call for reading descriptor
  12. What does fflush(stdin) do in C programing? [duplicate]
  13. Why does ENOENT mean “No such file or directory”?
  14. Merge multiple .so shared libraries
  15. How can I copy a file on Unix using C?
  16. How do I get a thread ID from an arbitrary pthread_t?
  17. Why does open() create my file with the wrong permissions?
  18. Printf is not working in C signal handler
  19. Calculating elapsed time in a C program in milliseconds
  20. Waiting for all child processes before parent resumes execution UNIX
  21. Recursive mkdir() system call on Unix
  22. Programmatically retrieving the absolute path of an OS X command-line app
  23. Does linux allow any system call to be made from signal handlers?
  24. Seeking a simple description regarding ‘file descriptor’ after fork()
  25. Dropping root privileges
  26. To check the E2BIG error condition in exec
  27. What can cause a “Resource temporarily unavailable” on sock send() command
  28. How do I get tcsetpgrp() to work in C?
  29. Oracle Pro*C/OCI install handlers for SIGSEGV/SIGABRT and friends – why, and how to disable?
  30. Unix O_CREAT flag without mode specified

Leave a Comment