Bug 70922 - [PIGLIT,radeonsi] SIGSEGV for shaders/glsl-vs-inline-explosion
Summary: [PIGLIT,radeonsi] SIGSEGV for shaders/glsl-vs-inline-explosion
Alias: None
Product: Mesa
Classification: Unclassified
Component: glsl-compiler (show other bugs)
Version: git
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Ian Romanick
QA Contact: Intel 3D Bugs Mailing List
Depends on:
Reported: 2013-10-27 16:09 UTC by Kai
Modified: 2019-09-18 19:45 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Full GDB backtrace and register dump (7.79 KB, text/plain)
2013-10-27 16:09 UTC, Kai

Description Kai 2013-10-27 16:09:34 UTC
Created attachment 88184 [details]
Full GDB backtrace and register dump

While running Piglit on radeonsi (full graphics stack detailed below) I encountered an crash in "shaders/glsl-vs-inline-explosion". See the attached GDB backtrace and register dump for more details.

GPU: "PITCAIRN" (ChipID = 0x6819)
Linux: 3.11.6
libdrm: 2.4.47
LLVM: SVN:trunk/r193475
libclc: Git:master/4c18120c1a
Mesa: Git:master/64c081e8b7
GLAMOR: Git:master/ba209eeef2
DDX: Git:master/f1dc677e79

Let me know if you need further information.

This might be similar to bug 70920 but this backtrace shows the crash in ir_rvalue, while attachment 88181 [details] for bug 70920 shows the crash in ir_variable::ir_variable. Therefore I filed a new bug, feel free to close this as a duplicate.
Comment 1 Kai 2014-03-22 18:43:15 UTC
glsl-vs-inline-explosionNot sure, whether this should be closed or not, but I don't see the test in todays Piglit run. And certainly not among the three crashed tests. (Same as bug 70920 really)
Comment 2 GitLab Migration User 2019-09-18 19:45:05 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/799.

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.