On 11/27/2016 02:34 PM, Jakub Wilk wrote: > Signed-off-by: Jakub Wilk <jwilk@xxxxxxxxx> Thanks, Jakub. Applied. Cheers, Michael > --- > man2/ptrace.2 | 6 +++--- > 1 file changed, 3 insertions(+), 3 deletions(-) > > diff --git a/man2/ptrace.2 b/man2/ptrace.2 > index bd76099..0ff73fa 100644 > --- a/man2/ptrace.2 > +++ b/man2/ptrace.2 > @@ -1600,7 +1600,7 @@ Note that all mentions > apply equally to > .BR PTRACE_SYSEMU_SINGLESTEP. > .LP > -However, even if the tracee is was continued using > +However, even if the tracee was continued using > .BR PTRACE_SYSCALL > , it is not guaranteed that the next stop will be a syscall-exit-stop. > Other possibilities are that the tracee may stop in a > @@ -1702,7 +1702,7 @@ always followed by syscall-exit-stop, > stop, or the tracee's death; > no other kinds of ptrace-stop can occur in between. > However, note that seccomp stops (see below) can cause syscall-exit-stops, > -without preceeding syscall-entry-stops. > +without preceding syscall-entry-stops. > If seccomp is in use, care needs > to be taken not to misinterpret such stops as syscall-entry-stops. > .LP > @@ -1781,7 +1781,7 @@ will cause syscall-exit-stops, > the system call number may be changed and any other modified registers > are visible to the to-be-executed system call as well). > Note that there may be, > -but need not have been a preceeding syscall-entry-stop. > +but need not have been a preceding syscall-entry-stop. > > After a > .BR PTRACE_EVENT_SECCOMP > -- Michael Kerrisk Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ Linux/UNIX System Programming Training: http://man7.org/training/ -- To unsubscribe from this list: send the line "unsubscribe linux-man" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
