From: Bjarni Ingi Gislason <bjarniig-2945IVfuVpf1P9xLtpHBDw@public.gmane.org>
To: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [patch], ptrace(2): Unnecessary escape before ">"
Date: Sun, 6 May 2012 20:02:17 +0000 [thread overview]
Message-ID: <20120506200217.GA1004@rhi.hi.is> (raw)
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
next reply other threads:[~2012-05-06 20:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-06 20:02 Bjarni Ingi Gislason [this message]
[not found] ` <20120506200217.GA1004-2945IVfuVpf1P9xLtpHBDw@public.gmane.org>
2012-05-06 20:51 ` [patch], ptrace(2): Unnecessary escape before ">" Michael Kerrisk (man-pages)
[not found] ` <CAKgNAki_0bW43ffUsYLtRG06_h_iaGbBg-tzxjczPnqS660sdg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-05-06 21:39 ` Bjarni Ingi Gislason
[not found] ` <20120506213950.GA2078-2945IVfuVpf1P9xLtpHBDw@public.gmane.org>
2012-05-06 21:43 ` Michael Kerrisk (man-pages)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120506200217.GA1004@rhi.hi.is \
--to=bjarniig-2945ivfuvpf1p9xltphbdw@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox