From: Stuart Brady <sdbrady@ntlworld.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [BUG] Crash in cirrus_do_copy() with cirrus_blt_srcpitch == 0
Date: Sat, 14 Mar 2009 14:01:40 +0000 [thread overview]
Message-ID: <20090314140140.GA22970@miranda.arrow> (raw)
Hi,
Windows NT 4.0 SP1 crashes in cirrus_do_copy() when attempting to
apply display settings (i.e. depth/resolution) at the following point:
Program received signal SIGFPE, Arithmetic exception.
[Switching to Thread 0x7f6197c066e0 (LWP 31336)]
0x000000000045d1cf in cirrus_bitblt_start (s=0x2ac8240)
at /home/sdb/src/qemu/qemu-svn/hw/cirrus_vga.c:733
733 sx = (src % ABS(s->cirrus_blt_srcpitch)) / depth;
(gdb) print s->cirrus_blt_srcpitch
$1 = 0
(gdb) print s->cirrus_blt_dstpitch
$2 = 1
I'm not sure whether NT is just being silly, here. If it is, then I
suppose we would need to add a check for srcpitch != 0 and dstpitch != 0
to BLTUNSAFE()...
Any thoughts?
Cheers,
--
Stuart Brady
next reply other threads:[~2009-03-14 14:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-14 14:01 Stuart Brady [this message]
2009-03-14 14:16 ` [Qemu-devel] [BUG] Crash in cirrus_do_copy() with cirrus_blt_srcpitch == 0 Stuart Brady
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=20090314140140.GA22970@miranda.arrow \
--to=sdbrady@ntlworld.com \
--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).