From: Avi Kivity <avi@redhat.com>
To: Matteo Signorini <84kvm84@gmail.com>
Cc: Matteo Signorini <signorinimatteo@gmail.com>, kvm@vger.kernel.org
Subject: Re: LEAVE emulation infinite loop
Date: Tue, 26 Apr 2011 11:50:17 +0300 [thread overview]
Message-ID: <4DB68749.5020803@redhat.com> (raw)
In-Reply-To: <BANLkTikzQrFEw_F51xM3XzO9EyNAsWY3tA@mail.gmail.com>
On 04/25/2011 12:05 PM, Matteo Signorini wrote:
> Hi to All,
>
> I fixed the previously highlighted error, calling the right pop
> emulation function
> but still get the same error, an infinite "leave" emulation loop.
> IMHO this is not an emulation error since x86_decode_insn and
> x86_emulate_insn return a correct value ( r=0 )
> so I don't understand what I'm doing wrong...
> could you please give me an hint to fix it?
No idea, sorry, you'll have to debug it.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2011-04-26 8:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-24 7:08 LEAVE emulation infinite loop Matteo Signorini
2011-04-24 7:14 ` Avi Kivity
2011-04-25 9:05 ` Matteo Signorini
2011-04-26 8:50 ` Avi Kivity [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=4DB68749.5020803@redhat.com \
--to=avi@redhat.com \
--cc=84kvm84@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=signorinimatteo@gmail.com \
/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).