[lkml]   [2002]   [Aug]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [patch] O(1) sys_exit(), threading, scalable-exit-2.5.31-A6

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_


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 13:28    [W:0.139 / U:0.284 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site