Bug 108365 - swr: segfault when running test case GLES2.functional.vertex_arrays.multiple_attributes.stride.3_float2_17_float2_17_float2_0
Summary: swr: segfault when running test case GLES2.functional.vertex_arrays.multiple...
Status: RESOLVED MOVED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/Gallium/swr (show other bugs)
Version: git
Hardware: Other All
: medium normal
Assignee: mesa-dev
QA Contact: mesa-dev
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-10-15 09:12 UTC by Gert Wollny
Modified: 2019-09-18 18:24 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments
glxinfo output (24.41 KB, text/plain)
2018-10-15 09:12 UTC, Gert Wollny 		Details
View All

Description Gert Wollny 2018-10-15 09:12:34 UTC 
Created attachment 142026 [details]
glxinfo output

valgrind backtrace: 

Test case 'dEQP-GLES2.functional.vertex_arrays.multiple_attributes.stride.3_float2_17_float2_17_float2_0'..
==27162== Invalid read of size 4
==27162==    at 0x916FD14: swr_update_derived(pipe_context*, pipe_draw_info const*) (swr_state.cpp:1291)
==27162==    by 0x916A692: swr_draw_vbo(pipe_context*, pipe_draw_info const*) (swr_draw.cpp:61)
==27162==    by 0x90C2BD4: u_vbuf_draw_vbo (u_vbuf.c:1449)
==27162==    by 0x941683A: st_draw_vbo (st_draw.c:236)
==27162==    by 0x957A9B3: vbo_draw_arrays (vbo_exec_array.c:406)
==27162==    by 0x957B699: vbo_exec_DrawArrays (vbo_exec_array.c:565)
==27162==    by 0x5E60D5: glu::CallLogWrapper::glDrawArrays(unsigned int, int, int) (gluCallLogWrapper.inl:1222)
==27162==    by 0x51A2E0: deqp::gls::ContextArrayPack::render(deqp::gls::Array::Primitive, int, int, bool, float, float) (glsVertexArrayTests.cpp:1189)
==27162==    by 0x5172BB: deqp::gls::MultiVertexArrayTest::iterate() (glsVertexArrayTests.cpp:2129)
==27162==    by 0x1689C9: deqp::gles2::TestCaseWrapper::iterate(tcu::TestCase*) (tes2TestPackage.cpp:91)
==27162==    by 0x7413C2: tcu::TestSessionExecutor::iterateTestCase(tcu::TestCase*) (tcuTestSessionExecutor.cpp:299)
==27162==    Address 0x4 is not stack'd, malloc'd or (recently) free'd  


Host: Intel Kabylake 
OS:   Ubuntu 18.04
Comment 1 Alok Hota 2018-11-02 19:04:17 UTC 
Thanks for the details! I'll look into this.
Comment 2 GitLab Migration User 2019-09-18 18:24:40 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/201.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.