From: "Filip Navara" <xnavara@volny.cz>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Windows build crash problem
Date: Wed, 12 Dec 2007 17:32:08 +0100 [thread overview]
Message-ID: <5b31733c0712120832i33a3cd93gf0f07e82edeb4f97@mail.gmail.com> (raw)
In-Reply-To: <200712121625.AA00056@your-04ece94a0d.m1.interq.or.jp>
[-- Attachment #1: Type: text/plain, Size: 1041 bytes --]
Actually somebody has already described the problem on the mailing list and
Paul Brook replied to that message. Hopefully you can find it in the
archives.
F.
On Dec 12, 2007 5:25 PM, 武田 俊也 <t-takeda@m1.interq.or.jp> wrote:
> Hi all.
>
> I encountered the crash problem with windows build on Core-Duo host.
> Qemu crashes in cpu_interrupt() called from host_alarm_handler() in vl.c
> because CPUState *env = next_cpu is null.
>
> I tried the patch to check env is not null in host_alarm_handler()
> and now qemu does not crash.
>
> CPUState *env = next_cpu;
> + if(env) {
> /* stop the currently executing cpu because a timer occured */
> cpu_interrupt(env, CPU_INTERRUPT_EXIT);
> #ifdef USE_KQEMU
> if (env->kqemu_enabled) {
> kqemu_cpu_interrupt(env);
> }
> #endif
> + }
> event_pending = 1;
> }
>
> This is very temporary patch and I need to investigate
> why next_cpu is null but sorry now I dont have enough time.
>
> Thanks,
> TAKEDA, toshiya
>
>
>
>
[-- Attachment #2: Type: text/html, Size: 1521 bytes --]
next prev parent reply other threads:[~2007-12-12 16:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-12 16:25 [Qemu-devel] Windows build crash problem 武田 俊也
2007-12-12 16:32 ` Filip Navara [this message]
2007-12-16 12:45 ` andrzej zaborowski
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=5b31733c0712120832i33a3cd93gf0f07e82edeb4f97@mail.gmail.com \
--to=xnavara@volny.cz \
--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).