From: Julian Stecklina <js@alien8.de>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH] Enable monitor commands in GDB stub
Date: Tue, 03 Feb 2009 05:16:47 +0100 [thread overview]
Message-ID: <87vdrsw3ww.fsf@tabernacle.localnet> (raw)
In-Reply-To: 18752.17539.868644.941088@tabernacle.localnet
Julian Stecklina <jsteckli@os.inf.tu-dresden.de> writes:
> Hello,
>
> I have added support for the qRcmd packet to the GDB stub. This lets
> you issue "monitor foo" in GDB and have it executed in qemu's monitor.
>
> A quick test suggests that it works fine, but I am quite new to the
> qemu codebase, so I don't know if calling 'monitor_handle_command'
> directly from the GDB stub violates any assumptions.
Any comments on the patch? I use it since I posted this patch in
December without problems.
Regards,
--
Julian Stecklina
Well, take it from an old hand: the only reason it would be easier to
program in C is that you can't easily express complex problems in C,
so you don't. - Erik Naggum (in comp.lang.lisp)
prev parent reply other threads:[~2009-02-03 4:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-10 22:36 [Qemu-devel] [PATCH] Enable monitor commands in GDB stub Julian Stecklina
2009-02-03 4:16 ` Julian Stecklina [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=87vdrsw3ww.fsf@tabernacle.localnet \
--to=js@alien8.de \
--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).