From: Daniel Jacobowitz <drow@mvista.com>
To: Chris Zankel <zankel@tensilica.com>
Cc: gdb@sources.redhat.com
Subject: Re: RFC: Available registers as a target property
Date: Tue, 17 May 2005 14:03:00 -0000 [thread overview]
Message-ID: <20050517140329.GA7337@nevyn.them.org> (raw)
In-Reply-To: <4283E829.1020008@tensilica.com>
On Thu, May 12, 2005 at 04:35:05PM -0700, Chris Zankel wrote:
> >The options are to tell GDB about this directly, or to have the OCD
> >tell GDB about the real properties of the target. I obviously prefer
> >the latter when possible, because it allows GDB to gracefully handle
> >binaries built for one configuration, and run on another configuration
> >where they still work (but may be somehow affected by state they can
> >not see).
>
> This actually goes back to your comment above - I think. How do you
> tread 'pseudo' registers? Would it make sense to add 'flags' to the
> 'set' command?
>
> set:<NAME>:<PROTOCOL NUMBER>[:<FLAGS>]
I don't think so, but I don't have a good idea of what you would use it
for. Do you want to give me an example?
> Oops... I wasn't sure if I was looking at our code or the original GDB
> sources. It looks like GDB has support for non-sequential pnums, but
> doesn't allow to assign them from gdbarch.
Correct - not yet. Soon I hope.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-05-17 14:03 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-06 16:20 Daniel Jacobowitz
2005-05-07 10:25 ` Eli Zaretskii
2005-05-07 16:19 ` Daniel Jacobowitz
2005-05-07 19:37 ` Eli Zaretskii
2005-05-09 15:37 ` Daniel Jacobowitz
2005-05-09 20:58 ` Eli Zaretskii
2005-05-07 16:04 ` Mark Kettenis
2005-05-09 16:20 ` Daniel Jacobowitz
2005-05-09 15:57 ` Paul Brook
2005-05-09 16:32 ` Daniel Jacobowitz
2005-05-09 21:33 ` Chris Zankel
2005-05-09 23:07 ` Daniel Jacobowitz
2005-05-10 0:23 ` Chris Zankel
2005-05-10 21:08 ` Daniel Jacobowitz
2005-05-12 23:35 ` Chris Zankel
2005-05-17 14:03 ` Daniel Jacobowitz [this message]
2005-05-10 0:54 ` Ramana Radhakrishnan
2005-05-10 21:14 ` Daniel Jacobowitz
2005-05-17 19:32 ` Daniel Jacobowitz
2005-05-18 9:29 ` Richard Earnshaw
2005-05-19 1:00 ` Daniel Jacobowitz
2005-05-20 14:54 ` Richard Earnshaw
2005-05-09 22:39 Paul Schlie
2005-05-10 0:03 Paul Schlie
2005-05-10 11:12 Paul Schlie
2005-05-17 23:08 Paul Schlie
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=20050517140329.GA7337@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=zankel@tensilica.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