From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1J2UVM-0003B5-PP for qemu-devel@nongnu.org; Wed, 12 Dec 2007 11:32:16 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1J2UVK-0003Ak-Jm for qemu-devel@nongnu.org; Wed, 12 Dec 2007 11:32:15 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1J2UVK-0003Ah-F4 for qemu-devel@nongnu.org; Wed, 12 Dec 2007 11:32:14 -0500 Received: from nf-out-0910.google.com ([64.233.182.189]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1J2UVJ-0004DQ-RQ for qemu-devel@nongnu.org; Wed, 12 Dec 2007 11:32:14 -0500 Received: by nf-out-0910.google.com with SMTP id 30so296786nfu.12 for ; Wed, 12 Dec 2007 08:32:08 -0800 (PST) Message-ID: <5b31733c0712120832i33a3cd93gf0f07e82edeb4f97@mail.gmail.com> Date: Wed, 12 Dec 2007 17:32:08 +0100 From: "Filip Navara" Sender: filip.navara@gmail.com Subject: Re: [Qemu-devel] Windows build crash problem In-Reply-To: <200712121625.AA00056@your-04ece94a0d.m1.interq.or.jp> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_1622_19891179.1197477128654" References: <200712121625.AA00056@your-04ece94a0d.m1.interq.or.jp> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org ------=_Part_1622_19891179.1197477128654 Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit Content-Disposition: inline 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, 武田 俊也 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 > > > > ------=_Part_1622_19891179.1197477128654 Content-Type: text/html; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit Content-Disposition: inline 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




------=_Part_1622_19891179.1197477128654--