From: Zhiyuan Shao <zyshao@hust.edu.cn>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] About QEMU debugging console
Date: Tue, 26 Oct 2010 20:22:34 +0800 [thread overview]
Message-ID: <488094999.01944@mail.hust.edu.cn> (raw)
Message-ID: <1288095754.2775.3.camel@zhiyuan-desktop> (raw)
Hi team,
I am a Qemu User, and using Qemu 0.13.0 to debugging the linux kernel
code (Qemu+GDB).
During the usage, I found the Qemu debugging console (i.e., entered by
pressing Ctl+Alt+2 in Qemu SDL window or by passing "-monitor stdio" to
Qemu in the command line) is rather difficult to use. It can not show
some important information, e.g., on i386 platform, which is my major
interest, it can not show IDT, GDT information. Regarding the page
mapping information, "info tlb" actually do a really bad job.
On this side, I think Bochs is good. Unfortunately, it seems do not
support gdb-stub debugging and general purpose debugging at the same
time.
I do not know if the Qemu team had made any plans to improve this? such
as embedding the bochs debugging alike functionalities in future Qemu
releases?
Thanks!
Zhiyuan
next reply other threads:[~2010-10-26 12:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1288095754.2775.3.camel@zhiyuan-desktop>
2010-10-26 12:22 ` Zhiyuan Shao [this message]
2010-10-26 18:59 ` [Qemu-devel] About QEMU debugging console Blue Swirl
[not found] ` <1288141845.2157.34.camel@zhiyuan-desktop>
2010-10-27 1:10 ` Zhiyuan Shao
2010-10-27 20:07 ` Blue Swirl
[not found] ` <1288232435.2180.7.camel@zhiyuan-desktop>
2010-10-28 2:20 ` Zhiyuan Shao
2010-10-28 10:59 ` Kevin Wolf
2010-10-28 12:36 ` [Qemu-devel] " Jan Kiszka
[not found] ` <1288320071.14023.13.camel@zhiyuan-desktop>
2010-10-29 2:41 ` Zhiyuan Shao
2010-10-29 7:32 ` Jan Kiszka
2010-10-31 10:49 ` Andreas Färber
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=488094999.01944@mail.hust.edu.cn \
--to=zyshao@hust.edu.cn \
--cc=qemu-devel@nongnu.org \
/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).