signals

I have written a segmentation fault handler, using sigsetjmp and siglongjmp. Once it goes to the signal handler, i invoke siglongjmp so that the faulty instruction is skipped. Problem is, i again want to cause SIGSEGV and go to the same handler, but now sigsetjmp will return 1. How to reset sigsetjmp? Here is my code: #include <stdio.h> #include <memory.h> #include <stdlib.h> #include <unistd.h> #include <sys/mman.h> #include <sys/types.h> #include <fcntl.h> #include <signal.h> #include <setjmp.h> sigjmp_buf env, env1; void SIGSEGV_handler(int signal) { printf("Segmentation fault caught\n");

I want to know what ORA-24550: signal received: [si_signo=6] means? I know this is an oracle error and may an oracle latest patch can solve the issue. When this error is triggered, like the scenario where this signal has to be handled or whether this error occur when my application has to handle something related to oracle and the application failed to do that. Wilfred Hughes This is a sign that your Oracle client has received a signal it wasn't expecting. The Oracle docs say: ORA-24550: unhandled signal #number received. string Cause: Serious error: signal received Action: Refer to the

Is it possible to find out the process id of the process which has caused some signal. In my scenario, I have multiple children of a process running, and I want to know which one of them sent the signal. It is (finally!) very simple with python 3. The following is tested with python 3.3.3: #! /usr/bin/python3 import signal import time, os def callme(num, frame): pass # register the callback: signal.signal(signal.SIGUSR1, callme) print("py: Hi, I'm %d, talk to me with 'kill -SIGUSR1 %d'" % (os.getpid(),os.getpid())) # wait for signal info: while True: siginfo = signal.sigwaitinfo({signal

I'm trying to ignore SIGTRAP. I have the following proof-of-concept code: #include <signal.h> #include <stdlib.h> int main(){ signal(SIGTRAP, SIG_IGN); write(1, "A", 1); asm("int3"); write(1, "B", 1); return 0; } When I run it, I expect to see "AB", but I see ATrace/breakpoint trap (core dumped) Why does my program terminate despite it ignoring SIGTRAP? According to this site a blocked/ignored signal is automatically unblocked inside the kernel code when it is raised. So if the same signal is raised repeatedly, an infinite loop will not happen. Instead the application is terminated on the

In detail, what happens when you press Ctrl-C in a terminal? Yes, I know that it sends SIGINT, but what steps does it take to get there? I have done some research so I think I understand most of the picture, but not all of it. For the sake of pedagogy, I will assume we are running a terminal emulator, xterm, in an X session. The terminal is running the Bash shell, and the shell is currently running some long running pipeline consisting of multiple processes in the foreground. I press Ctrl-C in the keyboard. X sends the keyboard event to xterm. xterm translates the Ctrl-C keyboard event and

i am using message queue as an ipc between 2 programs. Now i want to send data from one program to another using message queue and then intimate it through a signal SIGINT. I dont know how to send a signal from one program to another . Can anybody pls provide a sample code if they have the solution. #include <sys/types.h> #include <signal.h> int kill(pid_t pid, int sig); Signal in linux can be send using kill system call just check this link for documentation of kill system call and example. you can see man -2 kill also. and it's not advisable to use SIGINT use SIGUSR1 or SIGUSR2 Note that by