Trunk spits out tons of GL error 0X502 messages (GL_INVALID_OPERATION)

Bug #191940 reported by wrtlprnft
2
Affects Status Importance Assigned to Milestone
Armagetron Advanced
Fix Committed
Low
Manuel Moos

Bug Description

The latest trunk spits out tons of these onto the console when running (DEBUGLEVEL=3, the display list setting doesn't seem to matter). I don't see any rendering bugs, though.

The first of them has the following backtrace:
 #0 st_Breakpoint () at ../../src/tools/tError.cpp:48
 #1 0x082420bb in sr_CheckGLError () at ../../src/render/rGL.cpp:47
 #2 0x08242537 in glRenderer::End (this=0x885d750, force=true) at ../../src/render/rGLRender.cpp:131
 #3 0x08050e01 in RenderEnd (force=true) at ../../src/render/rRender.h:154
 #4 0x08079656 in gCycle::Render (this=0x8ee2c7c, cam=0x8e04838) at ../../src/tron/gCycle.cpp:4438
 #5 0x0815da9d in eGameObject::RenderAll (grid=0x87f4b0c, cam=0x8e04838) at ../../src/engine/eGameObject.cpp:838

Revision history for this message
Manuel Moos (z-man) wrote :

Yeah, most illegal operation still have valid results. You can disable the error reporting by simply commenting out the reporting code.

Revision history for this message
wrtlprnft (wrtlprnft) wrote :

I know, I just wanted to let you know in case this is a trunk-only problem or something that doesn't happen on your system. After all it isn't supposed to happen :-)

Revision history for this message
Manuel Moos (z-man) wrote :

Heh, the errors were caused by too much error checking :)

Changed in armagetronad:
assignee: nobody → z-man
importance: Undecided → Low
milestone: none → 0.3.2
status: New → Fix Committed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.