Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Josef Wolf <jw@raven.inka.de>
To: gdb@sourceware.org
Subject: Re: Definition of PT_TEXT_ADDR and friends.
Date: Wed, 21 Mar 2007 17:50:00 -0000	[thread overview]
Message-ID: <20070321174509.GG26951@raven.wolf.local> (raw)
In-Reply-To: <20070321111657.GC27561@caradoc.them.org>

On Wed, Mar 21, 2007 at 07:16:57AM -0400, Daniel Jacobowitz wrote:
> On Wed, Mar 21, 2007 at 08:14:12AM +0100, Josef Wolf wrote:

> > At least for uClinux, ptrace() is hardwired to the same values as in
> > linux-low.c.
> 
> For all architectures, really?  I'm surprised.

I was confused, so don't be surprised :-)  Every architecture has its
own implementation.

> > So probably the comment is right and the defined should
> > be moved into uClinux's uc0-patch.  But I don't see why the dependency
> > on uclibc define.
> 
> uClibc or the kernel.  It's not GDB's business to keep track of that.

I don't see how uclibc can provide them without kernel support.

> > > (I know the __UCLIBC_HAS_MMU__ is out of date - I'm going to fix that
> > > today)
> > 
> > Hmmm, what's the correct way to find out whether the cpu has mmu without
> > uclibc?  How does uclibc find out?
> 
> You configure it :-)  But they've renamed the configuration macro
> recently.

Shouldn't the kernel headers provide some appropriate macro?  There seem
to exist a CONFIG_MMU macro, but this is only checked and never set.


  reply	other threads:[~2007-03-21 17:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-20  6:50 Josef Wolf
2007-03-20 10:56 ` Daniel Jacobowitz
2007-03-21  7:20   ` Josef Wolf
2007-03-21 11:17     ` Daniel Jacobowitz
2007-03-21 17:50       ` Josef Wolf [this message]
2007-03-21 18:03         ` Daniel Jacobowitz

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=20070321174509.GG26951@raven.wolf.local \
    --to=jw@raven.inka.de \
    --cc=gdb@sourceware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox