From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1OBNjn-0003uo-94 for qemu-devel@nongnu.org; Mon, 10 May 2010 03:49:15 -0400 Received: from [140.186.70.92] (port=59879 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OBNgN-00062I-Ih for qemu-devel@nongnu.org; Mon, 10 May 2010 03:49:12 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OBNco-0006Ag-2w for qemu-devel@nongnu.org; Mon, 10 May 2010 03:45:33 -0400 Received: from mx1.redhat.com ([209.132.183.28]:51895) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OBNck-00069Z-3J for qemu-devel@nongnu.org; Mon, 10 May 2010 03:41:58 -0400 Message-ID: <4BE7B8C1.9060807@redhat.com> Date: Mon, 10 May 2010 10:41:53 +0300 From: Avi Kivity MIME-Version: 1.0 References: <4BE32178.2090103@msgid.tls.msk.ru> In-Reply-To: <4BE32178.2090103@msgid.tls.msk.ru> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Re: Another SIGFPE in display code, now in cirrus List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Michael Tokarev Cc: qemu-devel , KVM list On 05/06/2010 11:07 PM, Michael Tokarev wrote: > There was a bug recently fixed in vnc code. Apparently > there's something similar in the cirrus emulation as well. > Here it triggers _always_ (including old versions of kvm) > when running windows NT and hitting "test" button in its > display resolution dialog. Here's what gdb is to say: > > Program received signal SIGFPE, Arithmetic exception. > [Switching to Thread 0xf76cab70 (LWP 580)] > 0x080c5e45 in cirrus_do_copy (s=0x86134dc, dst=960000, src=0, w=2, h=9) > at hw/cirrus_vga.c:687 > 687 sx = (src % ABS(s->cirrus_blt_srcpitch)) / depth; > (gdb) p depth > $1 = 2 > (gdb) p s->cirrus_blt_srcpitch > $2 = 0 > > > This qemu-kvm-0.12.3 - actually a debian package of it, > but there's no patches relevant to video applied. > > Anything can be done with it? Well, it's trivial to check for the condition, but how to handle it? Need to find the spec for the chip. -- error compiling committee.c: too many arguments to function