Sponsored Content
Full Discussion: Signal catching
Top Forums Programming Signal catching Post 302259791 by dark_knight on Wednesday 19th of November 2008 03:00:25 AM
Old 11-19-2008
Signal catching

Hi!
I want to catch all signals that my program receives print their name and then execute the default handler.
Can you help me on that?

I've tried the following code:
Code:
#include <stdio.h>
#include <unistd.h>
#include <signal.h>

void (*hnd[32])(int i);

char signals[32][10] = 
{
    "SIGHUP", "SIGINT", "SIGQUIT", "SIGILL", "SIGTRAP", 
    "SIGABRT", "SIGEMT", "SIGFPE", "SIGKILL", "SIGBUS", 
    "SIGSEGV", "SIGSYS", "SIGPIPE", "SIGALRM", "SIGTERM", 
    "SIGURG", "SIGSTOP", "SIGTSTP", "SIGCONT", "SIGCHLD", 
    "SIGTTIN", "SIGTTOU", "SIGIO", "SIGXCPU", "SIGXFSZ", 
    "SIGVTALRM", "SIGPROF", "SIGWINCH", "SIGINFO", "SIGUSR1", 
    "SIGUSR2", "SIGTHR" 
}; //SIGTHR?

void handle(int i)
{
    printf("I've received the signal named: %s\n", signals[i-1]);
    hnd[i](i);
}

int main()
{

    int i;
    for ( i = 1; i < 32; i++ )
        hnd[i] = signal(i, handle);    

    for (;;) pause();

    return 0;
}

This works somehow, but after receiving a signal it displays the message and then receives a segmentation fault signal. Any ideas?
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

catching interrupts

hey i have been facing a problem,can you tell me if we can catch ctrl d in unix i have tried and sucessfully catched and disabled ctrl-c and ctrl -z but am not sure if we can do the same for CTRL-D, so got any clue mail on he forum or ...i mean c programming in Unix thats what i am working on (1 Reply)
Discussion started by: toughguy2handle
1 Replies

2. Programming

Catching signal and piping

Hi, Recently I was reading some c coding by some colleagues and I noticed that the above trend. They will create a pipe for the process then they will use the standard signal handler to capture a particular signal and write that signal to the pipe. On the other end, the process will read the... (7 Replies)
Discussion started by: joseph_ng
7 Replies

3. UNIX for Dummies Questions & Answers

Awk- catching the last two chars

Can anyone explain to me how to get the last two chars' from each row of Column (each row being variable in length) using awk, some of the lines will be blank, I'll be running a paste after awking. So I need to keep the blanks where they are..so I can paste back all columns in the correct order ... (9 Replies)
Discussion started by: Gerry405
9 Replies

4. Shell Programming and Scripting

Catching all Exit Codes

I have a Unix Script that has several exit in the middle. each returning seperate exit codes. I have to catch all the exit's and perform an operation say "Mail the status code" before the actual code completes. How can i do this in KSH ? (3 Replies)
Discussion started by: Sivaswami J
3 Replies

5. Shell Programming and Scripting

catching some errors

I need to find a way to keep a running tally of how many times events or actions occur. Say if a user is prompted to make inputs of 1 or 2, I want it to keep track of how many times 1 was entered, and how many times 2 was entered. Thanks for your help (5 Replies)
Discussion started by: bebop1111116
5 Replies

6. Programming

catching a signal from child process

i am creating children processes using fork system call every child i create goes to sleep for random time. when child stops running how can i catch his signal and turminate the child (2 Replies)
Discussion started by: emil2006
2 Replies

7. Shell Programming and Scripting

Catching errors

Hi, I'm writing a scheduling script which will co-ordinate the launching of scripts. This script is scheduling based on an input file, and launches the appropriate scripts at the right times. The only issue I'm having is: - if a script dies, or even has a syntax error, I want to catch... (1 Reply)
Discussion started by: GoldenEye4ever
1 Replies

8. Shell Programming and Scripting

Quiting running process without catching TRAP signal

Hi, I would like to ask, if is it possible to quit running loop in the script any other way than catching the trap signal. Ctrl-C ends only current running instance of process but not whole script. Any clues? (3 Replies)
Discussion started by: smoofy
3 Replies

9. Shell Programming and Scripting

Catching error in sftp

Hi All Experts, I have a script which logs to the server via sftp connection with below code :- user_name@sftp_server.com and the connection is going smooth. My requirement is to place file in sftp_server in some path. and if path doesn't exist or the file is not put successfully I... (3 Replies)
Discussion started by: punitsoneji
3 Replies
SIGACTION(2)							System Calls Manual						      SIGACTION(2)

NAME
sigaction, signal - manage signal state and handlers SYNOPSIS
#include <signal.h> int sigaction(int sig, const struct sigaction *act, struct sigaction *oact) void (*signal(int sig, void (*handler)(int)))(int); DESCRIPTION
Sigaction() is used to examine, set, or modify the attributes of a signal. The argument sig is the signal in question. The act argument points to a structure containing the new attributes of the signal, the structure pointed to by oact will receive the old attributes that were in effect before the call. The act and oact arguments may be NULL to indicate that either no new attributes are to be set, or that the old attributes are not of interest. The structure containing the signal attributes is defined in <signal.h> and looks like this: struct sigaction { void (*sa_handler)(int sig); sigset_t sa_mask; int sa_flags; }; The sa_handler field contains the address of a signal handler, a function that is called when the process is signalled, or one of these special constants: SIG_DFL Default signal handling is to be performed. This usually means that the process is killed, but some signals may be ignored by default. SIG_IGN Ignore the signal. The sa_mask field indicates a set of signals that must be blocked when the signal is being handled. Whether the signal sig itself is blocked when being handled is not controlled by this mask. The mask is of a "signal set" type that is to be manipulated by the sigset(3) functions. How the signal is handled precisely is specified by bits in sa_flags. If none of the flags is set then the handler is called when the sig- nal arrives. The signal is blocked during the call to the handler, and unblocked when the handler returns. A system call that is inter- rupted returns -1 with errno set to EINTR. The following bit flags can be set to modify this behaviour: SA_RESETHAND Reset the signal handler to SIG_DFL when the signal is caught. SA_NODEFER Do not block the signal on entry to the handler. SA_COMPAT Handle the signal in a way that is compatible with the the old signal() call. The old signal() signal system call sets a signal handler for a given signal and returns the old signal handler. No signals are blocked, the flags are SA_RESETHAND | SA_NODEFER | SA_COMPAT. New code should not use signal(). Note that signal() and all of the SA_* flags are Minix extensions. Signal handlers are reset to SIG_DFL on an execve(2). Signals that are ignored stay ignored. Signals Minix knows about the following signals: signal num notes description SIGHUP 1 k Hangup SIGINT 2 k Interrupt (usually DEL or CTRL-C) SIGQUIT 3 kc Quit (usually CTRL-) SIGILL 4 kc Illegal instruction SIGTRAP 5 xkc Trace trap SIGABRT 6 kc Abort program SIGFPE 8 k Floating point exception SIGKILL 9 k Kill SIGUSR1 10 k User defined signal #1 SIGSEGV 11 kc Segmentation fault SIGUSR2 12 k User defined signal #2 SIGPIPE 13 k Write to a pipe with no reader SIGALRM 14 k Alarm clock SIGTERM 15 k Terminate (default for kill(1)) SIGCHLD 17 pvi Child process terminated SIGCONT 18 p Continue if stopped SIGSTOP 19 ps Stop signal SIGTSTP 20 ps Interactive stop signal SIGTTIN 21 ps Background read SIGTTOU 22 ps Background write SIGWINCH 23 xvi Window size change The letters in the notes column indicate: k The process is killed if the signal is not caught. c The signal causes a core dump. i The signal is ignored if not caught. v Only Minix-vmd implements this signal. x Minix extension, not defined by POSIX. p These signals are not implemented, but POSIX requires that they are defined. s The process should be stopped, but is killed instead. The SIGKILL signal cannot be caught or ignored. The SIGILL and SIGTRAP signals cannot be automatically reset. The system silently enforces these restrictions. This may or may not be reflected by the attributes of these signals and the signal masks. Types POSIX prescribes that <sys/types.h> has the following definition: typedef int (*sighandler_t)(int) With this type the following declarations can be made: sighandler_t sa_handler; sighandler_t signal(int sig, sighandler_t handler); This may help you to understand the earlier declarations better. The sighandler_t type is also very useful in old style C code that is compiled by a compiler for standard C. SEE ALSO
kill(1), kill(2), pause(2), sigprocmask(2), sigsuspend(2), sigpending(2), sigset(3). DIAGNOSTICS
Sigaction() returns 0 on success or -1 on error. Signal() returns the old handler on success or SIG_ERR on error. The error code may be: EINVAL Bad signal number. EFAULT Bad act or oact addresses. AUTHOR
Kees J. Bot (kjb@cs.vu.nl) SIGACTION(2)
All times are GMT -4. The time now is 01:00 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy