Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@redhat.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sourceware.org
Subject: Re: RFC: Correct "paddr_t" in gdb_proc_service.h
Date: Wed, 15 Mar 2006 19:51:00 -0000	[thread overview]
Message-ID: <44186EF1.8070603@redhat.com> (raw)
In-Reply-To: <20060315163650.GA16226@nevyn.them.org>

Daniel Jacobowitz wrote:
> 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.
> 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 admit that I can't rememeber now what problem this solved; it may be
> nothing, just an inconsistency I noticed while working on N32 support. But I
> think it's a worthwhile change to match the prototypes in libthread_db from
> whence these functions are called.
> 
> Any comments on this change?
> 

Seems ok -- except the cast for target_read_memory
should be (CORE_ADDR) addr, n'est ce pas?


  reply	other threads:[~2006-03-15 19:46 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 [this message]
2006-03-15 22:34   ` Daniel Jacobowitz
2006-03-15 22:44 ` Mark Kettenis
2006-03-15 22:59   ` Daniel Jacobowitz
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=44186EF1.8070603@redhat.com \
    --to=msnyder@redhat.com \
    --cc=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