From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1K3doD-00062R-Fy
	for qemu-devel@nongnu.org; Tue, 03 Jun 2008 17:12:45 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1K3doA-000620-24
	for qemu-devel@nongnu.org; Tue, 03 Jun 2008 17:12:44 -0400
Received: from [199.232.76.173] (port=55262 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1K3do9-00061x-Sd
	for qemu-devel@nongnu.org; Tue, 03 Jun 2008 17:12:41 -0400
Received: from an-out-0708.google.com ([209.85.132.241]:49998)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <anthony@codemonkey.ws>) id 1K3do9-0007H3-MZ
	for qemu-devel@nongnu.org; Tue, 03 Jun 2008 17:12:41 -0400
Received: by an-out-0708.google.com with SMTP id d18so669594and.130
	for <qemu-devel@nongnu.org>; Tue, 03 Jun 2008 14:12:41 -0700 (PDT)
Message-ID: <4845B3BC.8070701@codemonkey.ws>
Date: Tue, 03 Jun 2008 16:12:28 -0500
From: Anthony Liguori <anthony@codemonkey.ws>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] [PATCH] gdbstub: monitor fixes v3
References: <4836FFCA.5000107@windriver.com>
In-Reply-To: <4836FFCA.5000107@windriver.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Reply-To: qemu-devel@nongnu.org
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.gnu.org/pipermail/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: qemu-devel@nongnu.org, Paul Brook <paul@codesourcery.com>

Jason Wessel wrote:
> Based on some comments in the qemu irc channel, here is a revised
> implementation of gdb monitor pass through patches.
>
> At a future time if it is truly "high value" the gdb specific monitor
> commands will be migrated into the qemu monitor, OR at such time that
> the user emulation begins to use the monitor.  Presently, the only
> user of the gdb specific variables is a debugger and the controls
> exist to alter the behavior from the debugger, even if you have to
> find the debugger console window some where in a debugger UI...
>
> I would guess the average user never uses the debugger.  Out of the
> small community of users that use the debugger probably even fewer
> will use these new controls. These type of controls are intended for
> extremely low level debugging, hence the reason they exist in the
> "Advanced Section" in the first place :-)
>
> please apply in order:
> gdb_single_step_monitor_cmd.patch
>   

Please separate patches in individual emails in the future.

In general, I don't like the approach this takes using the monitor 
multiplexing support to simulate the ability to have multiple monitors.  
Either we should properly support having multiple monitors, or we should 
dedicate the monitor to the gdb interface.

That is, I'd rather see this patch implemented as -monitor gdb then 
taking over the monitor like it does.  I'm concerned that the 
multiplexing is going to break monitor redirection when the GDB session 
is active.

Regards,

Anthony Liguori


> gdb_monitor_plus_qemu_monitor.patch
>
>
> Thanks,
> Jason.
>
>