From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org
Subject: Re: RFC: Correct "paddr_t" in gdb_proc_service.h
Date: Wed, 15 Mar 2006 22:59:00 -0000 [thread overview]
Message-ID: <20060315223629.GA25509@nevyn.them.org> (raw)
In-Reply-To: <200603152234.k2FMY7kd008466@elgar.sibelius.xs4all.nl>
On Wed, Mar 15, 2006 at 11:34:07PM +0100, Mark Kettenis wrote:
> > Date: Wed, 15 Mar 2006 11:36:50 -0500
> > From: Daniel Jacobowitz <drow@false.org>
> >
> > If there is no <proc_service.h>, GDB will typedef unsigned long to paddr_t,
> > which is then used in various libthread_db interfaces. Even when this code
> > was designed to work on Solaris systems in addition to GNU/Linux, this
> > wasn't right; Solaris doesn't provide a paddr_t that has anything to do with
> > libthread_db, only an unrelated one that deals with physical addressing.
>
> Yes indeed. On BSD paddr_t is an usnigned integer type used to store
> physical memory addresses
>
> > The type that glibc's libthread_db uses is psaddr_t, which is a pointer
> > type.
> >
> > When I wrote this patch (last year) I went through the original changelog
> > entries for this file from 2000; they suggest that this change is correct
> > and there should be no paddr_t references in GDB.
>
> I think that's right, and therefore I don't understand your change at all :(.
Well, we do have paddr_t references. Want me to replace them all with
psaddr_t references while I'm here? (The same casts will still be
necessary, since again, psaddr_t is a pointer type.)
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-03-15 22:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-15 17:01 Daniel Jacobowitz
2006-03-15 19:51 ` Michael Snyder
2006-03-15 22:34 ` Daniel Jacobowitz
2006-03-15 22:44 ` Mark Kettenis
2006-03-15 22:59 ` Daniel Jacobowitz [this message]
2006-03-15 23:40 ` Mark Kettenis
2006-03-16 0:21 ` Daniel Jacobowitz
2006-03-16 15:10 ` Michael Snyder
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=20060315223629.GA25509@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@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