Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Will Deacon <will.deacon@arm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] gdbserver: ARM: add support for uclinux
Date: Fri, 13 Apr 2012 14:59:00 -0000	[thread overview]
Message-ID: <4F883EE5.8080407@redhat.com> (raw)
In-Reply-To: <1334308067-2285-1-git-send-email-will.deacon@arm.com>

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.

Anyway, looks fine.

> ---
> 
> 2012-04-13  Will Deacon  <will.deacon@arm.com>
> 
> 	* linux-low.c: Define PT_TEXT_ADDR, PT_TEXT_END_ADDR and
> 	PT_DATA_ADDR for ARM targets.
> 
>  gdb/gdbserver/linux-low.c |    4 ++++
>  1 files changed, 4 insertions(+), 0 deletions(-)
> 
> diff --git a/gdb/gdbserver/linux-low.c b/gdb/gdbserver/linux-low.c
> index 043451d..c4b52e7 100644
> --- a/gdb/gdbserver/linux-low.c
> +++ b/gdb/gdbserver/linux-low.c
> @@ -4766,6 +4766,10 @@ linux_stopped_data_address (void)
>  #define PT_TEXT_ADDR     (0x10000*4)
>  #define PT_DATA_ADDR     (0x10004*4)
>  #define PT_TEXT_END_ADDR (0x10008*4)
> +#elif defined(__arm__)
> +#define PT_TEXT_ADDR 0x10000
> +#define PT_DATA_ADDR 0x10004
> +#define PT_TEXT_END_ADDR 0x10008
>  #endif
>  
>  /* Under uClinux, programs are loaded at non-zero offsets, which we need



-- 
Pedro Alves


  reply	other threads:[~2012-04-13 14:58 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 [this message]
2012-04-13 16:23   ` Will Deacon
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=4F883EE5.8080407@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=will.deacon@arm.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