recompile with `#undef SIGACTION', waithandler is not
called.
I should add that even with the sigaction(2) interface, without
the `sigprocmask' call, it still doesn't work, which suggests
that SIGCHLD is being blocked.
Can anyone explain why?
From reading man 3 signal, I get the following
I have a small test program which simply forks and execs
its command line arguments, but after the fork and before
the exec, it sends a SIGSTOP to the child. The parent then
sleeps for 3 seconds before exiting. However, a signal
handler for SIGCHLD has been installed and I was expecting
the parent
On Tue, 21 May 2013 15:24:26 +1000, Noel Hunt wrote:
If I recompile with `#undef SIGACTION', waithandler is not
called.
I should add that even with the sigaction(2) interface, without
the `sigprocmask' call, it still doesn't work, which suggests
that SIGCHLD is being blocked.
Can anyone
Greetings
FYI:
On or about August 1 I upgraded emacs to V. 24.x and when running it,
I found this error in a terminal:
GLib-WARNING **: In call to g_spawn_sync(), exit status of a child
process was requested but SIGCHLD action was set to SIG_IGN and ECHILD
was received by waitpid(), so
Keith Bottner wrote:
I am having a problem with SIGCHLD signals and their interaction with
sockets.
I have an application that forks modules in separate processes and use UNIX
domain sockets for communication. The main application handles the SIGCHLD
signal so that it can detect when
I am having a problem with SIGCHLD signals and their interaction with
sockets.
I have an application that forks modules in separate processes and use UNIX
domain sockets for communication. The main application handles the SIGCHLD
signal so that it can detect when/if a module crashes and if so
I am having a problem with SIGCHLD signals and their interaction with
sockets.
I have an application that forks modules in separate processes and use UNIX
domain sockets for communication. The main application handles the SIGCHLD
signal so that it can detect when/if a module crashes and if so
On Mon, Feb 10, 2003 at 07:52:06PM +0100, Alexander wrote:
I'm having a problem when running a program that forks a child.
The program handles SIGCHLD with its own function that calls waitpid().
So the program thinks that when SIGCHLD is raised then the child is terminated.
But the parent
Hello
I'm having a problem when running a program that forks a child.
The program handles SIGCHLD with its own function that calls waitpid().
So the program thinks that when SIGCHLD is raised then the child is terminated.
But the parent gets SIGCHLD even if the child is still running
