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 07:20:00 -0000 [thread overview]
Message-ID: <20070321071411.GF26951@raven.wolf.local> (raw)
In-Reply-To: <20070320105618.GA24723@caradoc.them.org>
On Tue, Mar 20, 2007 at 06:56:18AM -0400, Daniel Jacobowitz wrote:
> On Tue, Mar 20, 2007 at 07:44:56AM +0100, Josef Wolf wrote:
> > When compiling gdb for uClinux with armnommu, I noticed that (in
> > linux-low.c) PT_TEXT_ADDR, PT_DATA_ADDR and PT_TEXT_END_ADDR are
> > defined only when __mcoldfire__ is defined. I think this is wrong.
> > Instead, IMHO, it should always be defined when we have linux without
> > a mmu.
> >
> > Comments?
>
> /* These should really be defined in the kernel's ptrace.h header. */
>
> We don't know what to define them _to_ on other platforms. If you
> have another platform which fails to define them in the kernel
> headers, we can add another case.
At least for uClinux, ptrace() is hardwired to the same values as in
linux-low.c. 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.
> (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?
next prev parent reply other threads:[~2007-03-21 7:20 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 [this message]
2007-03-21 11:17 ` Daniel Jacobowitz
2007-03-21 17:50 ` Josef Wolf
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=20070321071411.GF26951@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