From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 28210] New: [bisected r300g] Heroes of Newerth crash
Date: Sat, 22 May 2010 01:39:40 -0700 (PDT) [thread overview]
Message-ID: <bug-28210-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=28210
Summary: [bisected r300g] Heroes of Newerth crash
Product: Mesa
Version: git
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/DRI/r300
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: drakkk@centrum.cz
Created an attachment (id=35792)
--> (https://bugs.freedesktop.org/attachment.cgi?id=35792)
backtrace
With latest mesa git Heroes of Newerth crash early in game usually if some
effect like when you gain level is rendered. This is a regression introduce by
this commit:
f86ac27bf9203fdd9b7110dc843263307f475a99 is the first bad commit
commit f86ac27bf9203fdd9b7110dc843263307f475a99
Author: Marek Olšák <maraeo@gmail.com>
Date: Sat May 15 22:55:17 2010 +0200
r300g: fix psychedelic colors with SWTCL
r300_vertex_shader::outputs was uninitialized.
Also remove the tokens parameter.
Reverting mentioned commit solves this issue.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2010-05-22 8:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-22 8:39 bugzilla-daemon [this message]
2010-05-22 8:40 ` [Bug 28210] [bisected r300g] Heroes of Newerth crash bugzilla-daemon
2010-05-22 8:44 ` bugzilla-daemon
2010-05-22 8:47 ` bugzilla-daemon
2010-05-23 16:52 ` bugzilla-daemon
2010-05-23 18:29 ` 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-28210-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