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.
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)
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)
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)
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)
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)
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)
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)
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)
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
LEARN ABOUT DEBIAN
semanage_bool_iterate_active
semanage_iterate(3) Libsemanage API documentation semanage_iterate(3)NAME
semanage_iterate - SELinux Management API
SYNOPSIS
The following iterate function is supported for any semanage record.
Replace the function and object name as necessary.
extern int ITERATE_FUNCTION (
semanage_handle_t *handle,
int (*handler) (
const semanage_OBJECT_t *object,
void *varg),
void *handler_arg);
DESCRIPTION
Behavior:
The iterate function will execute the specified handler over all objects in the selected location. An arbitrary argument can be
passed into the handler function along with each object.
The object passed in is property of the libsemanage library, and may not be modified or preserved - use semanage_OBJECT_clone if
that is necessary.
The handler code may not invoke any semanage write requests for the same object type (i.e. modifying the underlying store is not
allowed). The iterate function is reentrant only while inside a transaction (see semanage_begin_transaction ). It is not safe to
execute other semanage read or write requests within iterate if not inside a transaction. The handler may return -1 to signal error
exit, 0 to signal continue, and 1 to signal successful exit early (the iterate function will stop accordingly).
Parameters:
The handle is used to track persistent state across semanage calls, and for error reporting. The handler is the function to execute,
with handler_arg as its second parameter, and each object as its first parameter.
Requirements:
This function requires an semanage connection to be established (see semanage_connect(3) )
RETURN VALUE
In case of failure, -1 is returned, and the semanage error callback is invoked, describing the error. Otherwise a non-negative integer is
returned (a commit number). The same number will be returned by all other semanage object read calls until the next commit.
SEE ALSO semanage_handle_create(3), semanage_connect(3),
ivg2@cornell.edu 15 March 2006 semanage_iterate(3)
07-10-2009
