On Mon, 19 Aug 2002, Ingo Molnar wrote:
>
> the problem is that the debugger wants to do a wait4 as well, to receive
> the SIGSTOP result. Now if the original parent 'steals' the wait4 result,
> what will happen?
If a child has a debugger, it clearly is never "stopped" or "zombie" as
far as the parent is concerned, so the parent should either block, or it
should return -EAGAIN.
> this whole mess can only be fixed by decoupling the ptrace() mechanism
> from signals and wait4 completely
No, you only need to make debugged children slightly pecial in wait4(), in
that the parent must never see their state, only the fact that they are
there (as if they were still running, in short, regardless of their _real_
state)
Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Fri Aug 23 2002 - 22:00:18 EST