Re: [PATCH] cleanup ptrace stops and remove notify_parent

[Roland McGrath]

> Are you sure such a user visible semantic change is a good idea? 

Not if it's not too hard to avoid.  I think I can make it not come up by
converting TASK_STOPPED into TASK_TRACED when you use ptrace.  It will just
take some synchronization for that case.

> I at least have written (not very important, but existing) user space
> code in the past that assumed it can stop and single step without
> SIGCONT. I wouldn't be surprised if other debuggers ran into 
> the same issue.

I assume you mean stop with SIGSTOP, then attach with PTRACE_ATTACH, then
step with PTRACE_SINGLESTEP.  If you are already attached, then any stop
will report to you first in TASK_TRACED and never end up TASK_STOPPED
unless you explicitly pass a stop signal through with ptrace.


Thanks,
Roland

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/