Just in case, please ignore
[PATCH 54] PTRACE_SINGLESTEP shouldn't bypass SYSCALL_EXIT
[PATCH 55] workaround to pass the assert() at step-from-clone.c:193
patches. You were right, there are ugly even as temporary changes.
And unneeded.
Currently the code wrongly assumes that
On 09/23, Roland McGrath wrote:
It's a further oddity that you can single-step (or not) into the
system call and then get a ptrace stop inside it, that being for
PTRACE_EVENT_FORK et al. From there, the thread register state shows
it being after the syscall insn, but (in vanilla ptrace, and
