From: Simon.Richter@hogyros.de (Simon Richter)
To: linux-arm-kernel@lists.infradead.org
Subject: ptrace(PTRACE_PEEKUSER, ..., PT_TEXT_ADDR, ...)
Date: Wed, 1 Sep 2010 10:01:52 +0200 [thread overview]
Message-ID: <20100901080152.GA3474@richter> (raw)
In-Reply-To: <20100901071701.GC8142@n2100.arm.linux.org.uk>
Hi,
On Wed, Sep 01, 2010 at 08:17:01AM +0100, Russell King - ARM Linux wrote:
> > As has been pointed out by Andreas Schwab from SuSE, the code
> > responsible for returning the text segment address is never reached
> > because the lines immediately before the code added in the commit
> > already filter these out and return -EIO.
> I've always regarded this PT_* stuff as a hack around the problem at
> hand - and as you point out below...
Well, in principle the user page would be the right place for them, and
the PT_* defines allow accessing the struct members without requiring
"offsetof" or similar compiler extensions.
> ... it has the potential to break horribly when the original API is
> extended through additional hardware features.
Only as long as there are no struct members defined that will be carried
over to future versions. I have no real idea why the ARM port has this
hack.
> Maybe this is something which should be fixed properly by introducing
> a proper cross-arch API for getting this information.
The other architectures have added a proper member to struct user.
Simon
prev parent reply other threads:[~2010-09-01 8:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-20 12:41 ptrace(PTRACE_PEEKUSER, ..., PT_TEXT_ADDR, ...) Simon Richter
2010-09-01 7:17 ` Russell King - ARM Linux
2010-09-01 8:01 ` Simon Richter [this message]
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=20100901080152.GA3474@richter \
--to=simon.richter@hogyros.de \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.