[lkml]   [2004]   [Oct]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Subjectodd behaviour with SIGCHLD and CLD_TRAPPED
I've been playing around a bit with monitoring a child process.

If I send the child a SIGSTOP, the parent gets sent SIGCHLD with si_code == 5.
If I send SIGCONT, the parent gets si_code == 6.

So far so good.

However, if I attach gdb to the child, or detach gdb from the child, the parent
gets no notification. It would seem useful for the parent to know that this has
happened, so it knows that the child may not be running properly.

Is there any way to get this information?


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 14:07    [W:0.048 / U:13.308 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site