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@xxxxxxxxxxxxxxxxxx> --- 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@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
