From: Kevin Wolf <kwolf@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Bug 891002 <891002@bugs.launchpad.net>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Bug 891002] [NEW] windows mingw compiled qemu-system-x86_64 crash on startup
Date: Wed, 16 Nov 2011 12:00:21 +0100 [thread overview]
Message-ID: <4EC397C5.6090806@redhat.com> (raw)
In-Reply-To: <CAJSP0QUKsy+QV1FUU367Sfe-VKjhNXpZV+9cgme4By09i_Jm1w@mail.gmail.com>
Am 16.11.2011 11:35, schrieb Stefan Hajnoczi:
> On Wed, Nov 16, 2011 at 7:01 AM, humeafo <891002@bugs.launchpad.net> wrote:
>> Public bug reported:
>>
>> qemu-1.0-rc2/cpu-exec.c:37 longjmp(env->jmp_env, 1); it seems that env->jmp_env destroyed, (gdb) p env->jmp_env
>> $3 = {0, 0, 0, 36249608, 41418280, 5303318, 41418664, 0, 0, 0, 0, 0, 0, 0, 0, 0}
>
> Kevin: Is this similar to the issue you found with your mingw cross-compiler?
The symptoms were different. I didn't get a broken TCG state but some
internals of the Fiber used for coroutines must have been corrupted
(SwitchFiber() crashed when dereferencing a null pointer, but the
externally visible pointer that qemu passed to it was still ok).
Maybe both could be symptoms of the same kind of memory corruption.
Kevin
next prev parent reply other threads:[~2011-11-16 10:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-16 7:01 [Qemu-devel] [Bug 891002] [NEW] windows mingw compiled qemu-system-x86_64 crash on startup humeafo
2011-11-16 7:04 ` [Qemu-devel] [Bug 891002] " humeafo
2011-11-16 10:35 ` [Qemu-devel] [Bug 891002] [NEW] " Stefan Hajnoczi
2011-11-16 11:00 ` Kevin Wolf [this message]
2011-11-17 3:08 ` [Qemu-devel] [Bug 891002] " humeafo
2011-11-24 10:29 ` humeafo
2016-11-08 10:20 ` Thomas Huth
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=4EC397C5.6090806@redhat.com \
--to=kwolf@redhat.com \
--cc=891002@bugs.launchpad.net \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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).