From: Anoop <acv-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
To: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [patch] ptrace.2: Add note regarding 'struct user'
Date: Sat, 17 May 2008 06:43:09 -0400 [thread overview]
Message-ID: <20080517064309.gnqp888k2s8wo4sk@imap.linux.ibm.com> (raw)
A few days back Roland McGrath discussed about the ptrace
PTRACE_PEEKUSER behavior @ http://lkml.org/lkml/2008/5/8/375
Thought that adding a note saying - the offsets and data returned
might not match with the definition of struct user - will help.
Signed-off-by: Anoop Vijayan <acv-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
--- man-pages-2.79/man2/ptrace.2.orig 2008-05-17 12:54:50.000000000 +0530
+++ man-pages-2.79/man2/ptrace.2 2008-05-17 13:45:53.000000000 +0530
@@ -138,7 +138,7 @@ The word is returned as the result of th
.BR ptrace ()
call.
Typically the offset must be word-aligned, though this might vary by
-architecture. (\fIdata\fP is ignored.)
+architecture. See NOTES. (\fIdata\fP is ignored.)
.TP
.BR PTRACE_POKETEXT ", " PTRACE_POKEDATA
Copies the word
@@ -454,7 +454,9 @@ behavior.
the process with PID 1, may not be traced.
.LP
The layout of the contents of memory and the USER area are quite OS- and
-architecture-specific.
+architecture-specific. The offset supplied and the data returned might
+not entirely match with the definition of
+.I struct user
.LP
The size of a "word" is determined by the OS variant
(e.g., for 32-bit Linux it is 32 bits, etc.).
--
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:[~2008-05-17 10:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-17 10:43 Anoop [this message]
[not found] ` <20080517064309.gnqp888k2s8wo4sk-FJGp5E75HVmZamtmwQBW5tBPR1lH4CV8@public.gmane.org>
2008-05-21 17:53 ` [patch] ptrace.2: Add note regarding 'struct user' Michael Kerrisk
[not found] ` <483461B7.5090706-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2008-05-21 18:13 ` Roland McGrath
[not found] ` <20080521181307.DB90926FA24-nL1rrgvulkcB9AHHLWeGtNQXobZC6xk2@public.gmane.org>
2008-05-21 20:20 ` Michael Kerrisk
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=20080517064309.gnqp888k2s8wo4sk@imap.linux.ibm.com \
--to=acv-23vcf4htsmix0ybbhkvfkdbpr1lh4cv8@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