[patch], ptrace(2): Unnecessary escape before ">"

[patch], ptrace(2): Unnecessary escape before ">"

[Bjarni Ingi Gislason]

Package: man-pages
Version: 3.40
Severity: minor
Tags: patch

  From "groff -ww ..." (or "man --warnings=w ...":

<standard input>:758: warning: escape character ignored before `>'

  Also periods (full stop) in ellipises "protected" with "\&".

  Patch:

--- ptrace.2	2012-04-26 22:58:36.000000000 +0000
+++ ptrace.2.new	2012-05-06 01:13:38.000000000 +0000
@@ -76,7 +76,7 @@
 Ptrace commands are always sent to
 a specific tracee using a call of the form
 
-    ptrace(PTRACE_foo, pid, ...)
+    ptrace(PTRACE_foo, pid, \&...\&)
 
 where
 .I pid
@@ -752,7 +752,7 @@
 .I WSTOPSIG(status)
 macro can't be used to perform this examination,
 because it returns the value
-.IR "(status\>>8)\ &\ 0xff" .)
+.IR "(status>>8)\ &\ 0xff" .)
 .SS Signal-delivery-stop
 When a (possibly multithreaded) process receives any signal except
 .BR SIGKILL ,
@@ -1507,14 +1507,14 @@
 .LP
 .nf
 *** we get syscall-enter-stop in thread 1: **
-PID1 execve("/bin/foo", "foo" <unfinished ...>
+PID1 execve("/bin/foo", "foo" <unfinished \&...\&>
 *** we issue PTRACE_SYSCALL for thread 1 **
 *** we get syscall-enter-stop in thread 2: **
-PID2 execve("/bin/bar", "bar" <unfinished ...>
+PID2 execve("/bin/bar", "bar" <unfinished \&...\&>
 *** we issue PTRACE_SYSCALL for thread 2 **
 *** we get PTRACE_EVENT_EXEC for PID0, we issue PTRACE_SYSCALL **
 *** we get syscall-exit-stop for PID0: **
-PID0 <... execve resumed> )             = 0
+PID0 <...\& execve resumed> )             = 0
 .fi
 .LP
 If the

-- 
Bjarni I. Gislason
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [patch], ptrace(2): Unnecessary escape before ">"

[Michael Kerrisk (man-pages)]

Bjarni,

On Mon, May 7, 2012 at 8:02 AM, Bjarni Ingi Gislason <bjarniig-2945IVfuVpc@public.gmane.orgs> wrote:
> Package: man-pages
> Version: 3.40
> Severity: minor
> Tags: patch
>
>  From "groff -ww ..." (or "man --warnings=w ...":
>
> <standard input>:758: warning: escape character ignored before `>'
>
>  Also periods (full stop) in ellipises "protected" with "\&".

My knowledge here is a bit thin. Can you expand on the previous sentence please.

Thanks,

Michael


>
>  Patch:
>
> --- ptrace.2    2012-04-26 22:58:36.000000000 +0000
> +++ ptrace.2.new        2012-05-06 01:13:38.000000000 +0000
> @@ -76,7 +76,7 @@
>  Ptrace commands are always sent to
>  a specific tracee using a call of the form
>
> -    ptrace(PTRACE_foo, pid, ...)
> +    ptrace(PTRACE_foo, pid, \&...\&)
>
>  where
>  .I pid
> @@ -752,7 +752,7 @@
>  .I WSTOPSIG(status)
>  macro can't be used to perform this examination,
>  because it returns the value
> -.IR "(status\>>8)\ &\ 0xff" .)
> +.IR "(status>>8)\ &\ 0xff" .)
>  .SS Signal-delivery-stop
>  When a (possibly multithreaded) process receives any signal except
>  .BR SIGKILL ,
> @@ -1507,14 +1507,14 @@
>  .LP
>  .nf
>  *** we get syscall-enter-stop in thread 1: **
> -PID1 execve("/bin/foo", "foo" <unfinished ...>
> +PID1 execve("/bin/foo", "foo" <unfinished \&...\&>
>  *** we issue PTRACE_SYSCALL for thread 1 **
>  *** we get syscall-enter-stop in thread 2: **
> -PID2 execve("/bin/bar", "bar" <unfinished ...>
> +PID2 execve("/bin/bar", "bar" <unfinished \&...\&>
>  *** we issue PTRACE_SYSCALL for thread 2 **
>  *** we get PTRACE_EVENT_EXEC for PID0, we issue PTRACE_SYSCALL **
>  *** we get syscall-exit-stop for PID0: **
> -PID0 <... execve resumed> )             = 0
> +PID0 <...\& execve resumed> )             = 0
>  .fi
>  .LP
>  If the
>
> --
> Bjarni I. Gislason



-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Author of "The Linux Programming Interface"; http://man7.org/tlpi/
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [patch], ptrace(2): Unnecessary escape before ">"

[Bjarni Ingi Gislason]

On Mon, May 07, 2012 at 08:51:41AM +1200, Michael Kerrisk (man-pages) wrote:
> Bjarni,
> 
> On Mon, May 7, 2012 at 8:02 AM, Bjarni Ingi Gislason <bjarniig-5zMUtr2BsJg@public.gmane.org.is> wrote:
> > Package: man-pages
> > Version: 3.40
> > Severity: minor
> > Tags: patch
> >
> >  From "groff -ww ..." (or "man --warnings=w ...":
> >
> > <standard input>:758: warning: escape character ignored before `>'
> >
> >  Also periods (full stop) in ellipises "protected" with "\&".
> 
> My knowledge here is a bit thin. Can you expand on the previous sentence please.
> 

  This "protection" is actually only necessary, if the
(unprotected) ellipsis is at the start (becomes a groff macro
command) or (almost) at end of a line (last period interpreted as
an end of a sentence).  That can happen, if the paragraph (line)
gets later reformatted or changed in the source.

-- 
Bjarni I. Gislason
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [patch], ptrace(2): Unnecessary escape before ">"

[Michael Kerrisk (man-pages)]

Bjarni,

On Mon, May 7, 2012 at 9:39 AM, Bjarni Ingi Gislason <bjarniig-2945IVfuVpc@public.gmane.orgs> wrote:
> On Mon, May 07, 2012 at 08:51:41AM +1200, Michael Kerrisk (man-pages) wrote:
>> Bjarni,
>>
>> On Mon, May 7, 2012 at 8:02 AM, Bjarni Ingi Gislason <bjarniig@rhi.hi.is> wrote:
>> > Package: man-pages
>> > Version: 3.40
>> > Severity: minor
>> > Tags: patch
>> >
>> >  From "groff -ww ..." (or "man --warnings=w ...":
>> >
>> > <standard input>:758: warning: escape character ignored before `>'
>> >
>> >  Also periods (full stop) in ellipises "protected" with "\&".
>>
>> My knowledge here is a bit thin. Can you expand on the previous sentence please.
>>
>
>  This "protection" is actually only necessary, if the
> (unprotected) ellipsis is at the start (becomes a groff macro
> command) or (almost) at end of a line (last period interpreted as
> an end of a sentence).  That can happen, if the paragraph (line)
> gets later reformatted or changed in the source.

Ahh -- okay. It's not currently broken then, so I'll leave as is, but
I will apply the fix to  "\>>".

Thanks,

Michael


-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Author of "The Linux Programming Interface"; http://man7.org/tlpi/
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html