From: Daniel Jacobowitz <drow@mvista.com>
To: Paul Koning <pkoning@equallogic.com>
Cc: gdb@sources.redhat.com
Subject: Re: Looking for a gdb function to handle alias addresses
Date: Wed, 31 Dec 2003 16:37:00 -0000 [thread overview]
Message-ID: <20031231163751.GA18231@nevyn.them.org> (raw)
In-Reply-To: <16370.60074.841000.648191@gargle.gargle.HOWL>
On Wed, Dec 31, 2003 at 10:26:34AM -0500, Paul Koning wrote:
> >>>>> "Daniel" == Daniel Jacobowitz <drow@mvista.com> writes:
>
> Daniel> On Tue, Dec 30, 2003 at 05:19:57PM -0500, Paul Koning wrote:
> >> If this doesn't currently exist, could anyone offer hints as to
> >> where such a beast could be added (and what form, roughly, it
> >> should take)?
>
> Daniel> I can't imagine how you would do this. You'd need everywhere
> Daniel> that does symbol lookups to apply your theoretical method, at
> Daniel> the very least.
>
> So I take it the function I need doesn't exist at the moment.
>
> Should I interpret your comment as "don't even think about doing this,
> it's too ugly" or "sure you can do this but you'll have to insert the
> hook in a lot of places" ?
Take it as "I have no idea" :)
> If the latter, is another gdbarch function hook the right way?
Maybe. What you're describing is very system-specific, rather than
architecture-specific - I realize that the basic K0/K1 is a standard
MIPS feature, but the details of what regions alias will definitely
vary based on more than the gdbarch. So perhaps it should be directly
user-configurable instead.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-12-31 16:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-30 22:19 Paul Koning
2003-12-30 23:00 ` Daniel Jacobowitz
2003-12-31 15:26 ` Paul Koning
2003-12-31 16:37 ` Daniel Jacobowitz [this message]
2003-12-31 16:53 ` Paul Koning
2003-12-31 17:36 ` Andrew Cagney
2003-12-31 18:31 ` Paul Koning
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=20031231163751.GA18231@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=pkoning@equallogic.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