From: Craig Brozefsky <craig@red-bean.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] software breakpoints disappearing/reappearing in KVM/qemu
Date: Fri, 8 Apr 2011 15:37:46 -0500 [thread overview]
Message-ID: <BANLkTimDwzGHhrCaYfpohpjNA9uUeFeLrg@mail.gmail.com> (raw)
In-Reply-To: <BANLkTi=sshVc3+_v_Q02iHecfPU+jvPtiQ@mail.gmail.com>
On Fri, Apr 8, 2011 at 3:16 PM, Blue Swirl <blauwirbel@gmail.com> wrote:
> On Fri, Apr 8, 2011 at 9:50 PM, Craig Brozefsky <craig@red-bean.com> wrote:
>
> For KVM, native self-modifying code support of the CPU should be
> enough. Are you sure you are using KVM, what does "info kvm" tell?
Yup.
> How are you setting the breakpoint, with GDB interface?
Correct.
next prev parent reply other threads:[~2011-04-08 20:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-08 18:50 [Qemu-devel] software breakpoints disappearing/reappearing in KVM/qemu Craig Brozefsky
2011-04-08 20:16 ` Blue Swirl
2011-04-08 20:37 ` Craig Brozefsky [this message]
2011-04-08 20:52 ` [Qemu-devel] " Jan Kiszka
2011-04-10 14:01 ` Avi Kivity
2011-04-10 14:23 ` Jan Kiszka
2011-04-10 14:41 ` Avi Kivity
2011-04-10 15:16 ` Jan Kiszka
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=BANLkTimDwzGHhrCaYfpohpjNA9uUeFeLrg@mail.gmail.com \
--to=craig@red-bean.com \
--cc=blauwirbel@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).