[Mesa-dev] [Bug 105755] Mesa freezes when the GLSL shader contains a `for` loop with an uninitialized `i` index/counter variable

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=105755

Swyter <swyterzone+mesa3d at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |swyterzone+mesa3d at gmail.com

--- Comment #5 from Swyter <swyterzone+mesa3d at gmail.com> ---
Created attachment 138368
  --> https://bugs.freedesktop.org/attachment.cgi?id=138368&action=edit
game-log-with-debug-ogl-context-and-callback-no-undefined-warns.txt

@imirkin Looks like these GLSL warnings aren't exposed through
GL_ARB_debug_output/GL_KHR_debug callbacks. I originally developed the Linux
port using Mesa/radeonsi on a [AMD/ATI] Kaveri [Radeon R7 Graphics] (rev d4)
(PCI ID 1002:130f) and the warnings and error reporting always proved useful,
but that was before I implemented the dynamic lights part. I need to test if
the newer version of the game (with the attached shader) lock ups AMD/radeon
cards, too.

Anyway, thanks for the piglit tip. I'll use it from now on to lint my shaders,
hopefully they'll end up slightly less 'freezy'.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/mesa-dev/attachments/20180327/a91b9480/attachment.html>