From: Andrew Cagney <ac131313@cygnus.com>
To: Craig Hackney <craig@triscend.com>
Cc: "'gdb@sources.redhat.com'" <gdb@sources.redhat.com>
Subject: Re: Displaying more than 16 registers with GDB for ARM targets
Date: Sun, 12 May 2002 20:43:00 -0000 [thread overview]
Message-ID: <3CDF3650.7060708@cygnus.com> (raw)
In-Reply-To: <2407239113CD914CBA855A47698F01B062232C@SUGAH2.triscend.com>
> My main issue is that I didn't want to change the
> current ARM arch of GDB, rather I wanted to keep as much
> of it the same as I could but allow it to be extended to
> handle the the extra registers I have.
>
> So it sounds like, I have to hack into the current ARM arch
> to make it support my extra registers, this would mean that
> they would be displayed for all ARM targets. Even if the
> target does not support them.
>
> Or..
>
> Create a completely new architecture that is based 99% on the
> ARM, but has my extra register support.
>
> Am I missing something, or does that about sum it up?
A single GDB executable is capable of handling multiple architectures.
I can think of several ways of extending arm-tdep.c to support the extra
registers. Off hand:
- add a command to ``enable'' the registers
- have that command force an architecture change by calling
gdbarch_update_p().
- this will force a call to arm_gdbarch_init()
- that function is then free to re-layout the register cache the way you
want.
Andrew
next prev parent reply other threads:[~2002-05-13 3:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-10 10:02 Craig Hackney
2002-05-10 10:07 ` Richard Earnshaw
2002-05-12 20:43 ` Andrew Cagney [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-10 10:15 Craig Hackney
2002-05-01 19:57 Craig Hackney
2002-05-09 20:55 ` Andrew Cagney
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=3CDF3650.7060708@cygnus.com \
--to=ac131313@cygnus.com \
--cc=craig@triscend.com \
--cc=gdb@sources.redhat.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