From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 33196] New: r300g: crash after "implementation error ... should be mapped to ..." reports
Date: Sun, 16 Jan 2011 23:21:55 -0800 (PST) [thread overview]
Message-ID: <bug-33196-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=33196
Summary: r300g: crash after "implementation error ... should be
mapped to ..." reports
Product: Mesa
Version: git
Platform: x86 (IA32)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r300
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: gsr.bugs@infernal-iceberg.com
The application prints the following:
---8<---
Mesa 7.11-devel implementation error: glUniform1f should be mapped to 322, not
536
Please report at bugzilla.freedesktop.org
Mesa 7.11-devel implementation error: glColor3dv should be mapped to 330, not
12
Please report at bugzilla.freedesktop.org
Mesa 7.11-devel implementation error: glCopyPixels should be mapped to 307, not
255
--->8---
and crashes. Using git bisect I arrived at the following:
841ad6bfad27b2d8a196169b81235312a5e5f36a is the first bad commit
commit 841ad6bfad27b2d8a196169b81235312a5e5f36a
Author: Eric Anholt <eric@anholt.net>
Date: Fri Jan 14 14:03:52 2011 -0800
glapi: Regenerate for GL_ARB_ES2_compatibility.
:040000 040000 0d11d1581ed462e164fc88826df5e8174dc344e6
d09715fc1bee3d83a20e55e78e967e8fdf285fd4 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:[~2011-01-17 7:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-17 7:21 bugzilla-daemon [this message]
2011-01-17 7:32 ` [Bug 33196] r300g: crash after "implementation error ... should be mapped to ..." reports bugzilla-daemon
2011-01-17 7:48 ` 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-33196-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.