Sponsored Content
Top Forums Programming Signal Handling and Context Switches Post 302270080 by XComp on Friday 19th of December 2008 02:30:20 PM
Old 12-19-2008
What do you mean? How do install the signal handlers when using pthreads or setcontext etc?
 

10 More Discussions You Might Find Interesting

1. 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

2. UNIX for Advanced & Expert Users

signal handling in shell script

Hi can any please tell me is it possible to catch the signal in a shell script like we do in C. if yes please give me some idea or a link. (4 Replies)
Discussion started by: Raom
4 Replies

3. 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

4. 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

5. UNIX for Advanced & Expert Users

thread context switches: detection, prevention

#1: does anyone know how to detect how many times (and/or the time length) a given thread has been context switched out of the CPU? #2: are there any tchniques that minimize/eliminate your thread getting context switched? I would be happy to know the answers to these questions for ANY... (2 Replies)
Discussion started by: fabulous2
2 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. 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

8. Programming

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 #include <signal.h> #include<stdio.h> #include<stdlib.h> #include<string.h> char *j; void segv_handler(int dummy) { j=(char *)malloc(10); ... (4 Replies)
Discussion started by: pavan6754
4 Replies

9. 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

10. 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
Globus Callback Signal Handling(3)				   globus common				Globus Callback Signal Handling(3)

NAME
Globus Callback Signal Handling - Macros #define GLOBUS_SIGNAL_INTERRUPT Functions globus_result_t globus_callback_space_register_signal_handler (int signum, globus_bool_t persist, globus_callback_func_t callback_func, void *callback_user_arg, globus_callback_space_t space) globus_result_t globus_callback_unregister_signal_handler (int signum, globus_callback_func_t unregister_callback, void *unreg_arg) void globus_callback_add_wakeup_handler (void(*wakeup)(void *), void *user_arg) Detailed Description Macro Definition Documentation #define GLOBUS_SIGNAL_INTERRUPT Use this to trap interrupts (SIGINT on unix). In the future, this will also map to handle ctrl-C on win32. Function Documentation globus_result_t globus_callback_space_register_signal_handler (intsignum, globus_bool_tpersist, globus_callback_func_tcallback_func, void *callback_user_arg, globus_callback_space_tspace) Fire a callback when the specified signal is received. Note that there is a tiny delay between the time this call returns and the signal is actually handled by this library. It is likely that, if the signal was received the instant the call returned, it will be lost (this is normally not an issue, since you would call this in your startup code anyway) Parameters: signum The signal to receive. The following signals are not allowed: SIGKILL, SIGSEGV, SIGABRT, SIGBUS, SIGFPE, SIGILL, SIGIOT, SIGPIPE, SIGEMT, SIGSYS, SIGTRAP, SIGSTOP, SIGCONT, and SIGWAITING persist If GLOBUS_TRUE, keep this callback registered for multiple signals. If GLOBUS_FALSE, the signal handler will automatically be unregistered once the signal has been received. callback_func the user func to call when a signal is received callback_user_arg user arg that will be passed to callback space the space to deliver callbacks to. Returns: o GLOBUS_CALLBACK_ERROR_INVALID_SPACE o GLOBUS_CALLBACK_ERROR_INVALID_ARGUMENT o GLOBUS_SUCCESS otherwise globus_result_t globus_callback_unregister_signal_handler (intsignum, globus_callback_func_tunregister_callback, void *unreg_arg) Unregister a signal handling callback. Parameters: signum The signal to unregister. unregister_callback the function to call when the callback has been canceled and there are no running instances of it (may be NULL). This will be delivered to the same space used in the register call. unreg_arg user arg that will be passed to callback Returns: o GLOBUS_CALLBACK_ERROR_INVALID_ARGUMENT if this signal was registered with persist == false, then there is a race between a signal actually being caught and therefor automatically unregistered and the attempt to manually unregister it. If that race occurs, you will receive this error just as you would for any signal not registered. o GLOBUS_SUCCESS otherwise void globus_callback_add_wakeup_handler (void(*)(void *)wakeup, void *user_arg) Register a wakeup handler with callback library. This is really only needed in non-threaded builds, but for cross builds should be used everywhere that a callback may sleep for an extended period of time. An example use is for an io poller that sleeps indefinitely on select(). If the callback library receives a signal that it needs to deliver asap, it will call the wakeup handler(s), These wakeup handlers must run as though they were called from a signal handler (don't use any thread utilities). The io poll example will likely write a single byte to a pipe that select() is monitoring. This handler will not be unregistered until the callback library is deactivated (via common). Parameters: wakeup function to call when callback library needs you to return asap from any blocked callbacks. user_arg user data that will be passed along in the wakeup handler Author Generated automatically by Doxygen for globus common from the source code. Version 14.7 Tue Nov 27 2012 Globus Callback Signal Handling(3)
All times are GMT -4. The time now is 01:58 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy