From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 48535] New: Spurious GL_INVALID_OPERATION error generated by glColor()
Date: Tue, 10 Apr 2012 19:56:07 +0000 [thread overview]
Message-ID: <bug-48535-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=48535
Bug #: 48535
Summary: Spurious GL_INVALID_OPERATION error generated by
glColor()
Classification: Unclassified
Product: Mesa
Version: 7.10
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: minor
Priority: low
Component: Drivers/DRI/Radeon
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: i.am.inuyasha@gmail.com
Created attachment 59785
--> https://bugs.freedesktop.org/attachment.cgi?id=59785
Program that reproduces the issue
In some unknown circumstance glColor() can raise a GL_INVALID_OPERATION error,
which according to the manual should never happen. The attached program
reproduces the issue. It's generated from a log of GL calls made by another
program, so it's quite long (and some texture-related commands have been
stripped out, which I verified does not affect the result). The output I get
is:
Error 1282 at line 7353
which is consistent with the original program's issue - glColor() suddenly
raises this error after making all these GL calls.
--
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:[~2012-04-11 2:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-10 19:56 bugzilla-daemon [this message]
2012-04-11 12:42 ` [Bug 48535] Spurious GL_INVALID_OPERATION error generated by glColor() bugzilla-daemon
2012-04-11 12:43 ` bugzilla-daemon
2012-04-11 23:08 ` bugzilla-daemon
2012-04-12 2:44 ` 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-48535-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