stsignal(3) ShapeTools Toolkit Library stsignal(3)NAME
stCatchSigs, stInterruptAction, stQuitAction, stTermAction, stCleanup, stExit - signal handling
SYNOPSIS
#include <config.h>
#include <sttk.h>
void stCatchSigs (void);
Sfunc_t(*stInterruptAction)();
Sfunc_t(*stQuitAction)();
Sfunc_t(*stTermAction)();
void stCleanup (void);
void stExit (int exitCode);
DESCRIPTION
stCatchSigs activates a number of interrupt handlers, defined internally in the ShapeTools toolkit library. Interrupt handlers are defined
for the signals SIGINT, SIGQUIT, SIGFPE, SIGBUS, SIGSEGV, and SIGTERM. All interrupt handlers, except the one for SIGINT, cause program
termination after having done some cleanup work. The cleanup consists of removing all temporary files by calling stRmRegisteredFiles(3).
Some of the signal handlers are capable to execute functions defined by the application, while handling the interrupt. This mechanism is
activated by assigning a functions address to the appropriate variable. The following is a complete List.
Signal Variable
SIGINT stInterruptAction
SIGQUIT
stQuitAction
SIGTERM
stTermAction
stCleanup calls stRmRegisteredFiles(3) to remove all temporary files and the AtFS function af_cleanup(3) that orders AtFS's affairs.
stExit does the same as stCleanup and additionally end the program execution returning exitCode.
SEE ALSO
signal (3), stRmRegisteredFiles(3), af_cleanup(3).
sttk-1.7 Thu Jun 24 17:43:32 1993 stsignal(3)
Check Out this Related Man Page
stsignal(3) ShapeTools Toolkit Library stsignal(3)NAME
stCatchSigs, stInterruptAction, stQuitAction, stTermAction, stCleanup, stExit - signal handling
SYNOPSIS
#include <config.h>
#include <sttk.h>
void stCatchSigs (void);
Sfunc_t(*stInterruptAction)();
Sfunc_t(*stQuitAction)();
Sfunc_t(*stTermAction)();
void stCleanup (void);
void stExit (int exitCode);
DESCRIPTION
stCatchSigs activates a number of interrupt handlers, defined internally in the ShapeTools toolkit library. Interrupt handlers are defined
for the signals SIGINT, SIGQUIT, SIGFPE, SIGBUS, SIGSEGV, and SIGTERM. All interrupt handlers, except the one for SIGINT, cause program
termination after having done some cleanup work. The cleanup consists of removing all temporary files by calling stRmRegisteredFiles(3).
Some of the signal handlers are capable to execute functions defined by the application, while handling the interrupt. This mechanism is
activated by assigning a functions address to the appropriate variable. The following is a complete List.
Signal Variable
SIGINT stInterruptAction
SIGQUIT
stQuitAction
SIGTERM
stTermAction
stCleanup calls stRmRegisteredFiles(3) to remove all temporary files and the AtFS function af_cleanup(3) that orders AtFS's affairs.
stExit does the same as stCleanup and additionally end the program execution returning exitCode.
SEE ALSO
signal (3), stRmRegisteredFiles(3), af_cleanup(3).
sttk-1.7 Thu Jun 24 17:43:32 1993 stsignal(3)
For a program I am designing, which involves handling the keyboard input Ctrl^c (SIGINT), it is taking ages for the program to actually recognise and perform the corresponding action whenever I run it and hit Ctrl^C at the CL. I have to do at least 3 Ctrl^Cs before the program will actually... (3 Replies)
I have a problem with signal handlers not working.
I have a long 1000 line code and somehow this code for signal handling is not working:
$SIG{INT} = \&interrupt;
sub interrupt {
print STDERR "Caught a control c!\n";
exit; # or just about anything else you'd want to do
}
Any... (2 Replies)
hi,
in my application, i have set up to capture SIGINT and execute a handler.the problem is whenever i hit C-c, multiple SIGINT are sent to the application.I have blocked the SIGINT right after catching the first one but it is unsuccessful.Here is what i do :
jmp_buf main_loop;
int... (1 Reply)
I've read the man page of singal(3) but I still can't quite understand what is the difference between SIGINT, SIGALRM and SIGTERM.
Can someone tell me what is the behavioral difference among these 3 signals in kill command?
Thanks! (2 Replies)
Tried to add a function to my control_c interrupt here. It works but has one little bug. If the user selects to run the function instead of exiting, the program restarts itself without forking as it should. However, after that control_c no longer works again. I wanted to allow the user to run... (1 Reply)