From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 35483] New: util_blit_pixels_writemask: crash in line 322 of src/gallium/auxiliary/util/u_blit.c
Date: Mon, 21 Mar 2011 00:36:37 -0700 (PDT) [thread overview]
Message-ID: <bug-35483-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=35483
Summary: util_blit_pixels_writemask: crash in line 322 of
src/gallium/auxiliary/util/u_blit.c
Product: Mesa
Version: 7.10
Platform: x86 (IA32)
OS/Version: Linux (All)
Status: NEW
Severity: critical
Priority: medium
Component: Drivers/Gallium/r300
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: debian@carbon-project.org
Created an attachment (id=44648)
--> (https://bugs.freedesktop.org/attachment.cgi?id=44648)
Backtrace of the crash (Tropico with Wine 1.3.16)
When switching to (or starting a game when the last setting was) the hardware
accelerated mode in Tropico, the game immediately crashes with the attached
backtrace.
Please note, that I wasn't able to attach an GDB to Wine/Tropic, if I do, I get
tons of SIGSEGVs in Tropico before I get anywhere close to this bug. So I fear
the Wine-generated backtrace must do. If you need further information, beyond
the following, please let me know.
DDX: 6.14.0
X.org: 1.9.4.901 (1.9.5 RC 1)
Kernel: 2.6.38
libdrm2: 2.4.24
Mesa: 7.10
The "Severity" was set in accordance with
<https://bugs.freedesktop.org/page.cgi?id=fields.html#bug_severity> where a
crash is named as critical.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2011-03-21 7:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-21 7:36 bugzilla-daemon [this message]
2011-03-21 9:28 ` [Bug 35483] util_blit_pixels_writemask: crash in line 322 of src/gallium/auxiliary/util/u_blit.c bugzilla-daemon
2011-03-21 11:41 ` bugzilla-daemon
2011-03-29 22:53 ` bugzilla-daemon
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=bug-35483-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.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