From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 29311] New: [r300g]: Compiz crashes when trying to start it with latest mesa master.
Date: Thu, 29 Jul 2010 19:19:34 -0700 (PDT) [thread overview]
Message-ID: <bug-29311-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=29311
Summary: [r300g]: Compiz crashes when trying to start it with
latest mesa master.
Product: DRI
Version: unspecified
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: oreaus@gmail.com
Created an attachment (id=37448)
--> (https://bugs.freedesktop.org/attachment.cgi?id=37448)
compiz crash backtrace
I bisected and got this:
ba2cc3b8e6ad161181b67fd2575c6bc768584d23 is the first bad commit
commit ba2cc3b8e6ad161181b67fd2575c6bc768584d23
Author: Brian Paul <brianp@vmware.com>
Date: Thu Jul 29 13:49:21 2010 -0600
gallium: implement bounds checking for constant buffers
Plumb the constant buffer sizes down into the tgsi interpreter where
we can do bounds checking. Optional debug code warns upon out-of-bounds
reading. Plus add a few other assertions in the TGSI interpreter.
:040000 040000 7141c078038120e29bab2e275fb935f20731c0ff
e2f4d072421db8d000922127dc1f707145b73c61 M src
--
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:[~2010-07-30 2:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-30 2:19 bugzilla-daemon [this message]
2010-07-30 3:07 ` [Bug 29311] [r300g]: Compiz crashes when trying to start it with latest mesa master bugzilla-daemon
2010-08-01 5:17 ` bugzilla-daemon
2010-08-02 15:48 ` bugzilla-daemon
2010-08-02 23:49 ` bugzilla-daemon
2010-08-03 2:28 ` 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-29311-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