problem in SIGSEGV signal handling


 
Thread Tools Search this Thread
Top Forums Programming problem in SIGSEGV signal handling
# 1  
Old 07-06-2009
problem in SIGSEGV signal handling

i wrote handler for sigsegv such that i can allocate memory for a variable to which
sigsegv generated for illlegal acces of memory.

my code is

Code:
#include <signal.h>
#include<stdio.h>
#include<stdlib.h>
#include<string.h>
char *j;
void segv_handler(int dummy)
{
  j=(char *)malloc(10);
  strcpy(j,"hello");
  printf("segmentation fault mine j=%s\n",j);
}
main()
{
  signal(SIGSEGV, segv_handler);
  strcpy(j,"hello\n");
  printf("hai\n");
  for (;;)
  {
  }
}

output is :

Code:
segmentation fault mine j=hello
segmentation fault mine j=hello
segmentation fault mine j=hello
segmentation fault mine j=hello
segmentation fault mine j=hello
segmentation fault mine j=hello
segmentation fault mine j=hello
.......infinitely repeating above o/p

can i know why my program is behaving like this..
thanks in advance.....
# 2  
Old 07-06-2009
Have a read of this regarding signal handling:

http://beej.us/guide/bgipc/output/ht...e/signals.html

Regards
# 3  
Old 07-06-2009
The only calls you can safely make in a signal handler are those that are async-signal safe.

FWIW, malloc() and printf() are most certainly not async-signal safe.

What's probably happening is your SIGSEGV handler is also generating a SIGSEGV.
# 4  
Old 07-09-2009
It's not going to rewind your code back to the beginning of that line when the interrupt returns. It'll jump back into where the segfault happened, deep inside libc, which already has a copy of the variable that won't change when you change j. So, that's not going to work.

There's also a problem with calling library calls inside a signal handler. What if, for instance, a SIGSEGV happened right inside malloc(), causing a second malloc() to be called before the first one has finished? The heap may not even be in a valid state at that moment, or may be left in an invalid state when the second one returns. Nothing but system calls are signal-safe unless specifically written to avoid signal interference, and even then, not all system calls.

I also forsee another problem with this design of yours. The signal has no way to know what size buffer is needed. Why not just do this instead?

Code:
int main(void)
{
  j=strdup("hello\n");
}

This creates a correct-sized buffer containing "hello\n" for you. You can free it with free() later.
# 5  
Old 07-10-2009
MySQL

Quote:
Originally Posted by Corona688
It's not going to rewind your code back to the beginning of that line when the interrupt returns. It'll jump back into where the segfault happened, deep inside libc, which already has a copy of the variable that won't change when you change j. So, that's not going to work.

There's also a problem with calling library calls inside a signal handler. What if, for instance, a SIGSEGV happened right inside malloc(), causing a second malloc() to be called before the first one has finished? The heap may not even be in a valid state at that moment, or may be left in an invalid state when the second one returns. Nothing but system calls are signal-safe unless specifically written to avoid signal interference, and even then, not all system calls.

I also forsee another problem with this design of yours. The signal has no way to know what size buffer is needed. Why not just do this instead?

Code:
int main(void)
{
  j=strdup("hello\n");
}

This creates a correct-sized buffer containing "hello\n" for you. You can free it with free() later.
thanks for ur replay..
i got it.Smilie
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. AIX

Received signal #11, SIGSEGV [default] on AIX 6.1

Hello, One of our customer is getting segmentation fault when he runs his shell script which invokes our executable on AIX 6.1. On AIX 5.3, there were no issues. Here is the truss output. 811242: __loadx(0x0A040000, 0xF0D3A26C, 0x00000000, 0x00000009, 0x00000000) = 0xF026E884... (0 Replies)
Discussion started by: erra_krishna
0 Replies

2. Programming

problem in reforking and signal handling

hi friends i have a problem in signal handling ... let me explain my problem clearly.. i have four process .. main process forks two child process and each child process again forks another new process respectively... the problem is whenever i kill the child process it is reforking and the... (2 Replies)
Discussion started by: senvenugopal
2 Replies

3. UNIX and Linux Applications

SIGSEGV Signal handling

Hello, Can anybody tell me how can i handle segmentation fault signal, in C code? (2 Replies)
Discussion started by: mustus
2 Replies

4. Programming

Signal handling

I am trying to write a small program where I can send signals and then ask for an action to be triggered if that signal is received. For example, here is an example where I am trying to write a programme that will say you pressed ctrl*c when someone presses ctrl+c. My questions are what you would... (1 Reply)
Discussion started by: #moveon
1 Replies

5. Programming

signal handling while in a function other than main

Hi, I have a main loop which calls a sub loop, which finally returns to the main loop itself. The main loop runs when a flag is set. Now, I have a signal handler for SIGINT, which resets the flag and thus stops the main loop. Suppose I send SIGINT while the program is in subloop, I get an error... (1 Reply)
Discussion started by: Theju
1 Replies

6. Programming

signal handling question

Hello all, I am starting to learn signal handling in Linux and have been trying out some simple codes to deal with SIGALRM. The code shown below sets a timer to count down. When the timer is finished a SIGALRM is produced. The handler for the signal just increments a variable called count. This... (7 Replies)
Discussion started by: fox_hound_33
7 Replies

7. Shell Programming and Scripting

Signal handling in Perl

Guys, I'm doing signal handling in Perl. I'm trying to catch ^C signal inside the script. There two scripts : one shell script and one perl script. The shell script calls the perl script. For e.g. shell script a.sh and perl scipt sig.pl. Shell script a.sh looks something like this :... (6 Replies)
Discussion started by: obelix
6 Replies

8. Programming

Program received signal SIGSEGV, Segmentation fault.

Dear all, I used debugger from C++ and these are the message I got: Program received signal SIGSEGV, Segmentation fault. 0x00323fc0 in free () from /lib/tls/libc.so.6 (gdb) info s #0 0x00323fc0 in free () from /lib/tls/libc.so.6 #1 0x00794fa1 in operator delete () from... (5 Replies)
Discussion started by: napapanbkk
5 Replies

9. Programming

Signal Handling

Hi folks I'm trying to write a signal handler (in c on HPUX) that will catch the child process launched by execl when it's finished so that I can check a compliance file. The signal handler appears to catch the child process terminating however when the signal handler completes the parent... (3 Replies)
Discussion started by: themezzaman
3 Replies

10. UNIX for Advanced & Expert Users

Handling SIGUSR2 signal

HI, I need to handle SIGUSR2 signal in my application to change the state of the application dynamically. I have implemented the signal handler. However the application is able to catch only one SIGUSR2 signal. The second SIGUSR2 signal causes the application to crash. This is happning only with... (3 Replies)
Discussion started by: diganta
3 Replies
Login or Register to Ask a Question