[Bug 111114] gles cts-runner segfault compiling shader with textureGatherOffsets
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Fri Jul 12 05:14:22 UTC 2019
https://bugs.freedesktop.org/show_bug.cgi?id=111114
Bug ID: 111114
Summary: gles cts-runner segfault compiling shader with
textureGatherOffsets
Product: Mesa
Version: 19.1
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/DRI/i965
Assignee: intel-3d-bugs at lists.freedesktop.org
Reporter: mark.a.janes at intel.com
QA Contact: intel-3d-bugs at lists.freedesktop.org
Created attachment 144770
--> https://bugs.freedesktop.org/attachment.cgi?id=144770&action=edit
backtrace and shader text from crashing compile
When running the gles cts on mesa master, the test runner segfaults on tests
which pass when run individually. The same test will crash reliably via
cts-runner, but running the same config via the glcts executable will pass.
It takes about an hour on a kblgt3 to encounter the segfault, but this can be
accelerated by emptying out the test lists for various configs so that
cts-runner executes only the tests in
gl_cts/data/mustpass/gles/khronos_mustpass/3.2.5.x/gles31-khr-master.txt
Regardless of what test is crashing, the stack trace is the same (attached).
The compiler is attempting to format an error because it cannot find a matching
function for a textureGatherOffsets invocation. The parameter type list in the
ast has a corrupted type member, which can be seen in gdb.
Running valgrind on the cts-runner does not find memory errors, but the test
fails instead of segfaulting.
I was unable to bisect mesa because cts-runner fails to run on older commits
(eg 18.3). I applied a patch to cts to disable broken 565 configs, which did
not help the suite to run.
--
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-3d-bugs/attachments/20190712/842678e3/attachment-0001.html>
More information about the intel-3d-bugs
mailing list