All of lore.kernel.org
 help / color / mirror / Atom feed
* odd behaviour with SIGCHLD and CLD_TRAPPED
@ 2004-10-14 17:28 Chris Friesen
  0 siblings, 0 replies; only message in thread
From: Chris Friesen @ 2004-10-14 17:28 UTC (permalink / raw)
  To: Linux kernel

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?

Thanks,

Chris

^ permalink raw reply	[flat|nested] only message in thread
only message in thread, other threads:[~2004-10-14 18:26 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-10-14 17:28 odd behaviour with SIGCHLD and CLD_TRAPPED Chris Friesen

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.