From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 28654] New: [r300g] Every OpenGL application now either crashes on exit or fails to run at all.
Date: Mon, 21 Jun 2010 12:21:02 -0700 (PDT) [thread overview]
Message-ID: <bug-28654-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=28654
Summary: [r300g] Every OpenGL application now either crashes on
exit or fails to run at all.
Product: Mesa
Version: git
Platform: x86 (IA32)
OS/Version: All
Status: NEW
Severity: critical
Priority: medium
Component: Drivers/DRI/r300
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: rankincj@googlemail.com
Created an attachment (id=36404)
--> (https://bugs.freedesktop.org/attachment.cgi?id=36404)
backtrace from glxgears crash
No need to bisect this, there's only been one commit:
commit d82f6253331abf09ca714b844b1a9179ed8050b3
Author: Marek Olšák <maraeo@gmail.com>
Date: Mon Jun 21 00:42:06 2010 +0200
r300g: fix the KIL opcode for r3xx-r4xx (v4)
This is with my RV350. WoW now refuses to run at all:
err:module:attach_process_dlls "opengl32.dll" failed to initialize, aborting
err:module:LdrInitializeThunk Main exe initialization for L"H:\\World of
Warcraft\\WoW.exe" failed, status c0000005
And glxgears, celestia are now core-dumping on exit. It looks like there's a
NULL pointer problem. (See attachment.)
--
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-06-21 19:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-21 19:21 bugzilla-daemon [this message]
2010-06-21 19:47 ` [Bug 28654] [r300g] Every OpenGL application now either crashes on exit or fails to run at all bugzilla-daemon
2010-06-21 21:51 ` 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-28654-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.