All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zhiyuan Shao <zyshao@mail.hust.edu.cn>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Zhiyuan Shao <zyshao@hust.edu.cn>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Re: About QEMU debugging console
Date: Fri, 29 Oct 2010 10:41:11 +0800	[thread overview]
Message-ID: <488319284.02952@mail.hust.edu.cn> (raw)
Message-ID: <1288320071.14023.13.camel@zhiyuan-desktop> (raw)
In-Reply-To: <4CC96E31.3040503@siemens.com>

On Thu, 2010-10-28 at 14:36 +0200, Jan Kiszka wrote:
> Am 26.10.2010 14:22, Zhiyuan Shao wrote:
> > 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. 
> 
> Regarding usability in this scenario: You know that there is QEMU
> monitor pass-through via gdb "monitor" command?
> 
Yes, Just learned to use that. By gdb "monitor" command, the output of
QEMU debugging console is redirected to gdb. 

> > 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?
> 
> The most important lacking feature is proper system-level debugging
> support for gdb (via gdbstub). Once gdb has full access to all CPU
> states of the x86 targets, you can pretty-print whatever you want inside
> gdb via some nice Python scripts etc.
> 
Are you mean that it is the responsibility of gdb to parse the output
data of qemu built-in commands and generate user-friend output? Or grant
gdb full access to the target machine, which is emulated by Qemu, and it
is the responsibility of gdb again to generate easy-to-read output for
the users?

I think the first solution sounds more feasible, however, we still need
more helpful built-in commands in Qemu. 
And it is hard to implement the second solution: By doing this, we may
need to have full support from GDB community. 

Maybe, I am wrong. If possible, please give us more advices.

Thanks!

> Jan
> 

Zhiyuan

  reply	other threads:[~2010-10-29  2:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-26 12:22 [Qemu-devel] About QEMU debugging console Zhiyuan Shao
2010-10-26 12:22 ` Zhiyuan Shao
2010-10-26 18:59   ` Blue Swirl
2010-10-27  1:10     ` Zhiyuan Shao
2010-10-27  1:10       ` Zhiyuan Shao
2010-10-27 20:07         ` Blue Swirl
2010-10-28  2:20           ` Zhiyuan Shao
2010-10-28  2:20             ` Zhiyuan Shao
2010-10-28 10:59               ` Kevin Wolf
2010-10-28 12:36   ` [Qemu-devel] " Jan Kiszka
2010-10-29  2:41     ` Zhiyuan Shao [this message]
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=488319284.02952@mail.hust.edu.cn \
    --to=zyshao@mail.hust.edu.cn \
    --cc=jan.kiszka@siemens.com \
    --cc=qemu-devel@nongnu.org \
    --cc=zyshao@hust.edu.cn \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.