From: Jan Kiszka <jan.kiszka@siemens.com>
To: "Richard W.M. Jones" <rjones@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] How to capture guest %rip from a qemu process without monitor?
Date: Fri, 30 Sep 2011 10:49:20 +0200 [thread overview]
Message-ID: <4E858290.8000903@siemens.com> (raw)
In-Reply-To: <20110930074251.GA3972@amd.home.annexia.org>
On 2011-09-30 09:42, Richard W.M. Jones wrote:
>
> I've finally managed to reproduce a very infrequent kernel boot hang
> by forcing TCG (so it runs slower, bug seems to be timing sensitive)
> and running a boot test in a loop thousands of times.
>
> I'd like to find out where in the guest kernel this is looping.
>
> Unfortunately I don't have access to the monitor so "info registers"
> won't work, but I can attach to the qemu process with gdb.
>
> Which TCG struct contains %rip, other registers? What other useful
> information can be captured using only gdb?
Print first_cpu->eip, maybe also first_cpu->segs[1] to dump the CS
segment cache (relevant while in real mode).
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2011-09-30 8:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-30 7:42 [Qemu-devel] How to capture guest %rip from a qemu process without monitor? Richard W.M. Jones
2011-09-30 8:49 ` Jan Kiszka [this message]
2011-09-30 9:03 ` Richard W.M. Jones
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=4E858290.8000903@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=qemu-devel@nongnu.org \
--cc=rjones@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 NNTP newsgroup(s).