From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=46158 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1PBRiN-00062N-2X
	for qemu-devel@nongnu.org; Thu, 28 Oct 2010 08:36:20 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <jan.kiszka@siemens.com>) id 1PBRiL-0001WK-EW
	for qemu-devel@nongnu.org; Thu, 28 Oct 2010 08:36:18 -0400
Received: from thoth.sbs.de ([192.35.17.2]:18154)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <jan.kiszka@siemens.com>) id 1PBRiL-0001W1-2P
	for qemu-devel@nongnu.org; Thu, 28 Oct 2010 08:36:17 -0400
Message-ID: <4CC96E31.3040503@siemens.com>
Date: Thu, 28 Oct 2010 14:36:01 +0200
From: Jan Kiszka <jan.kiszka@siemens.com>
MIME-Version: 1.0
References: <488094999.01944@mail.hust.edu.cn>
In-Reply-To: <488094999.01944@mail.hust.edu.cn>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: [Qemu-devel] Re: About QEMU debugging console
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Zhiyuan Shao <zyshao@hust.edu.cn>
Cc: qemu-devel <qemu-devel@nongnu.org>

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?

> 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.

Jan

-- 
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux