From: Daniel Jacobowitz <drow@false.org>
To: James Yu <cyu021@gmail.com>
Cc: gdb-discuss@gnu.org, gdb@sources.redhat.com
Subject: Re: [Gdb-discuss] How to debug vmlinux and gdb itself at the same time ?
Date: Wed, 16 Mar 2005 14:38:00 -0000 [thread overview]
Message-ID: <20050316143835.GA26932@nevyn.them.org> (raw)
In-Reply-To: <60bb9541050316061351d55169@mail.gmail.com>
This is not the right list to ask GDB questions; redirected to gdb@.
On Wed, Mar 16, 2005 at 10:13:49PM +0800, James Yu wrote:
> Since current "info all-registers" provided in gdb doesn't output the
> values of hardware registers CR0, CR1, CR2, CR3, CR4, GDTR, LDTR and
> etc... I backtraced the gdb with gdb itself and tried to see how gdb
> retrieves hardware register values, so I can get the content of the
> registers previously mentioned myself.
GDB doesn't support those registers; a future version may, but updates
to your kgdb stub would also be required.
> However, when I traced up to "registers_info()" in gdb/infcmd.c:1596,
> the first test of "if (!targt_has_registers)" failed. Then I came up
> with an idea of debugging a gdb that is debugging a vmlinux (so I'll
> have some registers to print out in the inner gdb env), just I don't
> know whether it works and how to carry it out.
>
> Or maybe there are other ways to get the registers mentioned above ?
You can debug a GDB doing anything, just like any other program. For
instance, "gdb --args gdb vmlinux".
--
Daniel Jacobowitz
CodeSourcery, LLC
parent reply other threads:[~2005-03-16 14:38 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <60bb9541050316061351d55169@mail.gmail.com>]
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=20050316143835.GA26932@nevyn.them.org \
--to=drow@false.org \
--cc=cyu021@gmail.com \
--cc=gdb-discuss@gnu.org \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).