<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Mesa freezes when the GLSL shader contains a `for` loop with an uninitialized `i` index/counter variable" href="https://bugs.freedesktop.org/show_bug.cgi?id=105755#c8">Comment # 8</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Mesa freezes when the GLSL shader contains a `for` loop with an uninitialized `i` index/counter variable" href="https://bugs.freedesktop.org/show_bug.cgi?id=105755">bug 105755</a> from <a class="email" href="mailto:imirkin@alum.mit.edu" title="Ilia Mirkin <imirkin@alum.mit.edu>"> Ilia Mirkin</a> <pre>(In reply to Swyter from <a href="show_bug.cgi?id=105755#c5">comment #5</a>) > Created <a href="attachment.cgi?id=138368" name="attach_138368" title="game-log-with-debug-ogl-context-and-callback-no-undefined-warns.txt">attachment 138368</a> <a href="attachment.cgi?id=138368&action=edit" title="game-log-with-debug-ogl-context-and-callback-no-undefined-warns.txt">[details]</a> > 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 That's very surprising. This stuff goes through _mesa_glsl_warning which in turn should emit a DEBUG_TYPE_OTHER message. Are you sure that you don't get a callback with that? (Or perhaps you have it just filtering to ERROR's?)</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>