From: chimeranet89@gmail.com
To: Jan Kiszka <jan.kiszka@web.de>,
qemu-devel <qemu-devel@nongnu.org>,
Jun Koi <junkoi2004@gmail.com>
Subject: [Qemu-devel] Re: Re: [Bug 581353] Re: qemu doesn't stop execution upon hitting a breakpoint
Date: Wed, 16 Jun 2010 08:04:19 +0000 [thread overview]
Message-ID: <001485f7cb123bcf2f0489212b53@google.com> (raw)
In-Reply-To: <4C18837D.1050409@web.de>
[-- Attachment #1: Type: text/plain, Size: 206 bytes --]
Ok this is it:
I've just compiled and tried qemu 0.12.4, this bug has been fixed and it
works perfectly again, I'm adding a report to launchpad within the next few
seconds.. Thank you for the support.
[-- Attachment #2: Type: text/html, Size: 219 bytes --]
prev parent reply other threads:[~2010-06-16 8:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <00163649a20d7ed8cb048920f1e0@google.com>
2010-06-16 7:55 ` [Qemu-devel] Re: [Bug 581353] Re: qemu doesn't stop execution upon hitting a breakpoint Jan Kiszka
2010-06-16 8:04 ` chimeranet89 [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=001485f7cb123bcf2f0489212b53@google.com \
--to=chimeranet89@gmail.com \
--cc=jan.kiszka@web.de \
--cc=junkoi2004@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).