Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
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 v2] gdbserver: uclinux: pull in ptrace offset definitions from asm/ptrace.h
Date: Thu, 26 Apr 2012 16:10:00 -0000	[thread overview]
Message-ID: <20120426160926.GA20186@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <4F99718A.2090703@redhat.com>

On Thu, Apr 26, 2012 at 05:02:18PM +0100, Pedro Alves wrote:
> On 04/26/2012 04:54 PM, Will Deacon wrote:
> > 
> > diff --git a/gdb/gdbserver/linux-low.c b/gdb/gdbserver/linux-low.c
> > index 35d7e69..93d1f36 100644
> > --- a/gdb/gdbserver/linux-low.c
> > +++ b/gdb/gdbserver/linux-low.c
> > @@ -4772,6 +4772,8 @@ linux_stopped_data_address (void)
> >  #define PT_TEXT_ADDR     (0x10000*4)
> >  #define PT_DATA_ADDR     (0x10004*4)
> >  #define PT_TEXT_END_ADDR (0x10008*4)
> > +#else
> > +#include <asm/ptrace.h>
> >  #endif
> 
> 
> I'd much rather we include asm/ptrace.h unconditionally at the top, and wrap the
> existing #defines in (a single) #ifndef PT_TEXT_ADDR.  That'll allow easily trimming
> that section in a few years time, if/when we bump the minimum kernel version
> required past a version that is known to define those for those archs.  If that breaks
> one of those archs, we'll hear about it soon enough, don't sweat about it.  :-)

Right-o. I did actually try that initially but it gets fairly ugly if you
want to deal with the case where only a subset of the #defines exist in the
header. If breaking these archs isn't a big concern up-front, then I'm happy
just to test PT_TEXT_ADDR for each of them and be done with it. Plus, that
should take care of the sane configurations.

Will


  reply	other threads:[~2012-04-26 16:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-26 15:56 Will Deacon
2012-04-26 16:05 ` Pedro Alves
2012-04-26 16:10   ` Will Deacon [this message]
2012-04-26 18:28     ` Pedro Alves

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=20120426160926.GA20186@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