From: Jan Kiszka <jan.kiszka@web.de>
To: Andi Kleen <andi@firstfloor.org>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: qemu gdbstub
Date: Mon, 31 Aug 2009 09:42:48 +0200 [thread overview]
Message-ID: <4A9B7EF8.3030808@web.de> (raw)
In-Reply-To: <20090829080206.GA26468@one.firstfloor.org>
[-- Attachment #1: Type: text/plain, Size: 658 bytes --]
Andi Kleen wrote:
> Hi,
>
> The new qemu gdbstub in recent qemus/kvms is really nice and a
> big improvement over earlier ones. Thank you.
>
> I'm using qemu-kvm-0.10.6 on the plain Linux 2.6.30 KVM on VT.
>
> One problem I noticed is that I cannot step on another CPU thread
> than where it stopped.
>
> e.g.
>
> Ctrl-C
> (stopping on thread 1)
> (gdb) thread 2
> (gdb) step
> ...
> I come back to thread 1 after the step
>
> On native gdb with multiple threads that seems to work.
You need vCont support in the gdbstub, and this feature is now finally
merged into 0.11. So qemu-kvm-0.11-rcX should be what you want.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]
prev parent reply other threads:[~2009-08-31 7:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-29 8:02 [Qemu-devel] qemu gdbstub Andi Kleen
2009-08-31 7:42 ` Jan Kiszka [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=4A9B7EF8.3030808@web.de \
--to=jan.kiszka@web.de \
--cc=andi@firstfloor.org \
--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).