From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: MingyanGuo <guomingyan@gmail.com>
Subject: Re: [Qemu-devel] Could any body fix the bug in gdbstub.c for x86_64?
Date: Wed, 9 May 2007 23:59:48 +0100 [thread overview]
Message-ID: <200705092359.50136.paul@codesourcery.com> (raw)
In-Reply-To: <1fa17f810705090611o3355056hd9782dcca3f89ef8@mail.gmail.com>
On Wednesday 09 May 2007, MingyanGuo wrote:
> Hi,
> The -s option for qemu-system-x86_64 is not useable.
> I've already post a patch, but it is ignored.
> http://lists.gnu.org/archive/html/qemu-devel/2007-05/msg00062.html
Please read the list archives for previous patches/discussions on this topic.
Your patch is wrong in several ways
Paul
prev parent reply other threads:[~2007-05-09 23:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-09 13:11 [Qemu-devel] Could any body fix the bug in gdbstub.c for x86_64? MingyanGuo
2007-05-09 13:46 ` [Qemu-devel] " Jan Kiszka
2007-05-09 15:16 ` MingyanGuo
2007-05-09 22:59 ` Paul Brook [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=200705092359.50136.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=guomingyan@gmail.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).