From: Daniel Jacobowitz <drow@false.org>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: gdb@sourceware.org
Subject: Re: Towards better x86 system debugging support
Date: Tue, 06 Jan 2009 15:14:00 -0000 [thread overview]
Message-ID: <20090106151415.GA6512@caradoc.them.org> (raw)
In-Reply-To: <4961D487.1030707@web.de>
On Mon, Jan 05, 2009 at 10:36:07AM +0100, Jan Kiszka wrote:
> o Roughly, what code changes are required to exchange some i386.xml or
> x86-64.xml?
- Verification of the supplied registers in gdbarch init.
- Changes to hardcoded register numbers to always access pseudo
registers relative to gdbarch_num_regs, which will no longer be
constant.
If you agree with Mark that we should add the MSRs as a separate
address space rather than into the register cache it's a bit
trickier. I have relevant patches somewhere...
> o If gdb accepted such a static XML description from some x86 target,
> would it already stick with the register layout even when setting the
> arch manually (or later automatically)?
I don't remember whether set arch overrides just the arch, or the
entire target description. But probably the former.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2009-01-06 15:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-04 13:34 Jan Kiszka
2009-01-05 3:44 ` Daniel Jacobowitz
2009-01-05 8:52 ` GDB MI and actual type of a pointer or reference Elmenthaler, Jens
2009-01-05 9:36 ` Towards better x86 system debugging support Jan Kiszka
2009-01-06 15:14 ` Daniel Jacobowitz [this message]
2009-01-05 20:20 ` Mark Kettenis
2009-01-06 12:13 ` Jan Kiszka
2009-05-29 19:20 ` Samuel Bronson
2009-05-31 9:36 ` Jan Kiszka
2009-01-06 23:59 ` Doug Evans
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=20090106151415.GA6512@caradoc.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=jan.kiszka@web.de \
/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