From: Jan Kiszka <jan.kiszka@web.de>
To: guomingyan@gmail.com
Cc: qemu-devel@nongnu.org, Paul Brook <paul@codesourcery.com>
Subject: [Qemu-devel] Re: Could any body fix the bug in gdbstub.c for x86_64?
Date: Wed, 09 May 2007 15:46:21 +0200 [thread overview]
Message-ID: <4641D0AD.8060500@web.de> (raw)
In-Reply-To: <1fa17f810705090611o3355056hd9782dcca3f89ef8@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1030 bytes --]
MingyanGuo wrote:
> Hi,
> The -s option for qemu-system-x86_64 is not useable.
> I've already post a patch, but it is ignored.
Have you seen my patch [1] on this already? Does it work for you? It's
running fine here, but there are still some open questions [2], and I
unfortunately didn't received feedback on my last revisions as well.
I haven't looked in details at your approach, but you stumbled over the
same thing as I did, that redefining the register constants would
simplify things significantly - if this is fine with the rest of qemu.
> http://lists.gnu.org/archive/html/qemu-devel/2007-05/msg00062.html
> This patch is for version 0.9.0, could some body merge it
> in the cvs tree?
>
However the solution will finally look like, a fix for the next release
would be welcome here as well! One just need to know which way is
preferred...
Jan
[1] http://lists.gnu.org/archive/html/qemu-devel/2007-04/msg00554.html
[2] http://lists.gnu.org/archive/html/qemu-devel/2007-04/msg00524.html
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]
next prev parent reply other threads:[~2007-05-09 13:55 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 ` Jan Kiszka [this message]
2007-05-09 15:16 ` [Qemu-devel] " MingyanGuo
2007-05-09 22:59 ` [Qemu-devel] " Paul Brook
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=4641D0AD.8060500@web.de \
--to=jan.kiszka@web.de \
--cc=guomingyan@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.