Results for valgrind/fbo/fbo-luminance-alpha

Returncode: 0

Errors:
==20159== Invalid read of size 4
==20159==    at 0x4AC35DF: prepare_wm_surfaces (brw_wm_surface_state.c:594)
==20159==    by 0x4AAC3AE: brw_validate_state (brw_state_upload.c:397)
==20159==    by 0x4A98165: brw_draw_prims (brw_draw.c:361)
==20159==    by 0x4B9553B: vbo_draw_arrays (vbo_exec_array.c:588)
==20159==    by 0x804CDC5: piglit_draw_rect (piglit-util.c:748)
==20159==    by 0x804B329: piglit_display (fbo-luminance-alpha.c:86)
==20159==    by 0x804D846: display (piglit-framework.c:52)
==20159==    by 0x40C1C1D: fghcbDisplayWindow (freeglut_main.c:210)
==20159==    by 0x40C558F: fgEnumWindows (freeglut_structure.c:394)
==20159==    by 0x40C202D: glutMainLoopEvent (freeglut_main.c:249)
==20159==    by 0x40C2934: glutMainLoop (freeglut_main.c:1498)
==20159==    by 0x804D9E3: main (piglit-framework.c:118)
==20159==  Address 0x0 is not stack'd, malloc'd or (recently) free'd
==20159== 
==20159== 
==20159== Process terminating with default action of signal 11 (SIGSEGV): dumping core
==20159==  Access not within mapped region at address 0x0
==20159==    at 0x4AC35DF: prepare_wm_surfaces (brw_wm_surface_state.c:594)
==20159==    by 0x4AAC3AE: brw_validate_state (brw_state_upload.c:397)
==20159==    by 0x4A98165: brw_draw_prims (brw_draw.c:361)
==20159==    by 0x4B9553B: vbo_draw_arrays (vbo_exec_array.c:588)
==20159==    by 0x804CDC5: piglit_draw_rect (piglit-util.c:748)
==20159==    by 0x804B329: piglit_display (fbo-luminance-alpha.c:86)
==20159==    by 0x804D846: display (piglit-framework.c:52)
==20159==    by 0x40C1C1D: fghcbDisplayWindow (freeglut_main.c:210)
==20159==    by 0x40C558F: fgEnumWindows (freeglut_structure.c:394)
==20159==    by 0x40C202D: glutMainLoopEvent (freeglut_main.c:249)
==20159==    by 0x40C2934: glutMainLoop (freeglut_main.c:1498)
==20159==    by 0x804D9E3: main (piglit-framework.c:118)
==20159==  If you believe this happened as a result of a stack
==20159==  overflow in your program's main thread (unlikely but
==20159==  possible), you can try to increase the size of the
==20159==  main thread stack using the --main-stacksize= flag.
==20159==  The main thread stack size used in this run was 8388608.
Segmentation fault


Output: