Messages in this thread | | | Date | Wed, 1 Jun 2011 21:01:17 +0200 | From | Oleg Nesterov <> | Subject | Re: [PATCH 11/17] ptrace: implement PTRACE_SEIZE |
| |
On 05/30, Tejun Heo wrote: > > implements a new ptrace request PTRACE_SEIZE which attaches and traps > tracee
it doesn't trap the tracee ;)
> * PTRACE_SEIZE, unlike ATTACH, doesn't force tracee to trap. After > attaching tracee continues to run unless a trap condition occurs.
OK.
Just to remind, tracehook_report_clone() shouldn't send SIGSTOP if the auto-attached tracee is PT_SEIZED.
> * If PTRACE_SEIZE'd, group stop uses PTRACE_EVENT_STOP trap which uses > exit_code of (SIGTRAP | PTRACE_EVENT_STOP << 8) instead of the > stopping signal number
Hmm. May be it would be better to report stopping_signal | PTRACE_EVENT_STOP instead... I am not sure yet, but it seems this way we can avoid the PTRACE_GETSIGINFO changes. I'll try to explain later, when I finsh the reading.
Oleg.
| |