For example, wait_consider_task(). Even some tracehooks, say,
tracehook_notify_death() need task_is_ptraced().
Not some, just that one, right? So these are all really the same one
thing: ptrace interfering with normal parent wait/SIGCHLD.
In previous iterations, we had tracehook_inhibit_wait
On 07/22, Roland McGrath wrote:
serves for attach/detach. You need somewhere to store the
PTRACE_SETOPTIONS state and so forth, sure. But you can probably just
handle the attachedness at the utrace level. That's what
UTRACE_ATTACH_EXCLUSIVE is for.
Yes. As for -ptrace, I think
serves for attach/detach. You need somewhere to store the
PTRACE_SETOPTIONS state and so forth, sure. But you can probably just
handle the attachedness at the utrace level. That's what
UTRACE_ATTACH_EXCLUSIVE is for.
Yes. As for -ptrace, I think it should die. The only problem is
