From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org, Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] [PATCH] gdbstub: monitor fixes v3
Date: Tue, 03 Jun 2008 16:12:28 -0500 [thread overview]
Message-ID: <4845B3BC.8070701@codemonkey.ws> (raw)
In-Reply-To: <4836FFCA.5000107@windriver.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.
>
>
prev parent reply other threads:[~2008-06-03 21:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-23 17:32 [Qemu-devel] [PATCH] gdbstub: monitor fixes v3 Jason Wessel
2008-06-03 21:12 ` Anthony Liguori [this message]
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=4845B3BC.8070701@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=paul@codesourcery.com \
--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).