From: Will Deacon <will.deacon@arm.com>
To: Pedro Alves <palves@redhat.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] gdbserver: ARM: add support for uclinux
Date: Fri, 13 Apr 2012 16:23:00 -0000 [thread overview]
Message-ID: <20120413155949.GC4605@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <4F883EE5.8080407@redhat.com>
On Fri, Apr 13, 2012 at 03:57:41PM +0100, Pedro Alves wrote:
> On 04/13/2012 10:07 AM, Will Deacon wrote:
>
> > When debugging a uclinux target, it is necessary to retrieve the text
> > and data offsets of the running program in order for symbol resolution
> > to work correctly.
> >
> > This patch defines PT_{TEXT,DATA,TEXT_END}_ADDR for ARM, which can be
> > issued as `magic' addresses to the PTRACE_PEEKUSER request in order to
> > retrieve the child offsets.
>
>
> Is this for older kernels? I see these defined in
> arch/arm/include/asm/ptrace.h in current mainline.
Actually, it's for bleeding-edge kernels (3.4-rc2) since the ptrace request
has been broken until recently (it would return -EIO).
Although the #defines are exported in the kernel headers, they don't seem to
be picked up by sys/ptrace.h, which is why I followed the same path as the
other architectures here. An alternative would be to include asm/ptrace.h
directly and introduce guards for the other architectures to avoid duplicate
#defines...
...or would you expect libc to throw these out in its headers?
Cheers,
Will
next prev parent reply other threads:[~2012-04-13 16:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-13 9:11 Will Deacon
2012-04-13 14:59 ` Pedro Alves
2012-04-13 16:23 ` Will Deacon [this message]
2012-04-13 16:28 ` Pedro Alves
2012-04-13 17:02 ` Will Deacon
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=20120413155949.GC4605@mudshark.cambridge.arm.com \
--to=will.deacon@arm.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
/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