<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#c7">Comment # 7</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 Ian Romanick from <a href="show_bug.cgi?id=105755#c6">comment #6</a>) > Swyter: Can you run your program in gdb, interrupt it during the hang, and > provide a backtrace? > > Reading Ilia's response, it seems that the trivial glslsparsertest based > test case doesn't reproduce the hang. I guess a shader-runner test that > tries to draw with the shader would... glslparsertest just parses. The hang is just due to a very long shader loop (sometimes, I'd guess, depending what 'i' happens to get initialized to... like MIN_INT, it'll be looping for a while). gdb would just show it hung in "waiting for draw to complete".</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>