<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - r600g: 'invalid read' linking geometry shader" href="https://bugs.freedesktop.org/show_bug.cgi?id=74717#c16">Comment # 16</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - r600g: 'invalid read' linking geometry shader" href="https://bugs.freedesktop.org/show_bug.cgi?id=74717">bug 74717</a> from <a class="email" href="mailto:b.bellec@gmail.com" title="Benjamin Bellec <b.bellec@gmail.com>"> Benjamin Bellec</a> <pre>(In reply to <a href="show_bug.cgi?id=74717#c12">comment #12</a>) > I'm not able to reproduce it (tested with RV770 and CYPRESS) with current > master Mesa 10.2.0-devel (git-f74cf5f). Forget my comment about RV770, I realized I'm stuck to GL3.0 with it (due to lack of kernel support on my system). That said, with my CYPRESS, glxinfo say: OpenGL renderer string: Gallium 0.4 on AMD CYPRESS OpenGL core profile version string: 3.3 (Core Profile) Mesa 10.2.0-devel (git-7125473) OpenGL core profile shading language version string: 3.30 But when I launch this two gl-320 tests, I got nothing (no error, no window)... However, if I override GL version envvar, I got this: $ MESA_GL_VERSION_OVERRIDE=3.2 MESA_GLSL_VERSION_OVERRIDE=150 ./build/Release/gl-320-primitive-sprite OpenGL Version Needed 3.2 ( 3.2 Found ) => seems to work, I can play with the four pictures, zoom, etc. $ MESA_GL_VERSION_OVERRIDE=3.2 MESA_GLSL_VERSION_OVERRIDE=150 ./build/Release/gl-320-primitive-shading OpenGL Version Needed 3.2 ( 3.2 Found ) 0:22(34): error: length called on unsized array 0:24(23): error: unsized array index must be constant 0:25(18): error: unsized array index must be constant Erreur de segmentation (core dumped) => I got a black screen during 1 or 2 seconds and then close with a segfault. Note that I can launch Unigine Valley (which requires GL3.2 or GL3.3 I don't remember) without problem and without overriding the GL version envvar.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>