[Mesa-dev] [Bug 70920] [GLSL compiler] SIGSEGV for shaders/glsl-fs-inline-explosion

2019-09-18 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=70920

GitLab Migration User  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |MOVED

--- Comment #8 from GitLab Migration User  ---
-- 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/798.

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev

[Mesa-dev] [Bug 70920] [GLSL compiler] SIGSEGV for shaders/glsl-fs-inline-explosion

2014-09-29 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=70920

Ian Romanick i...@freedesktop.org changed:

   What|Removed |Added

 CC||huax...@intel.com

--- Comment #7 from Ian Romanick i...@freedesktop.org ---
*** Bug 84215 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev


[Mesa-dev] [Bug 70920] [GLSL compiler] SIGSEGV for shaders/glsl-fs-inline-explosion

2014-09-15 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=70920

--- Comment #5 from Erik Faye-Lund kusmab...@gmail.com ---
Created attachment 106343
  -- https://bugs.freedesktop.org/attachment.cgi?id=106343action=edit
error-checking in glsl-compiler

What's going on here, seems to be that we're running out of memory while
linking the shader (during optimizations, but that's probably just dumb luck).
This makes ralloc_size return a NULL-pointer, which gets dereferenced because
the only guards against NULL-pointers in the compiler seems to be asserts.

The attached patch fixes *that* issue for me, but it doesn't make the test
pass, nor fail gracefully either; all that happens is that piglit itself runs
out of memory, triggering an assert.

Besides, it doesn't seem like exceptions is exactly good style in this project.
So I dunno...

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev


[Mesa-dev] [Bug 70920] [GLSL compiler] SIGSEGV for shaders/glsl-fs-inline-explosion

2014-09-15 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=70920

Erik Faye-Lund kusmab...@gmail.com changed:

   What|Removed |Added

 Attachment #106343|0   |1
is obsolete||

--- Comment #6 from Erik Faye-Lund kusmab...@gmail.com ---
Created attachment 106345
  -- https://bugs.freedesktop.org/attachment.cgi?id=106345action=edit
error-checking in glsl-compiler

Adding a try-catch block around the lifespan around mem_ctx seems to have
helped, now the test plain fails instead of crashing.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev


[Mesa-dev] [Bug 70920] [GLSL compiler] SIGSEGV for shaders/glsl-fs-inline-explosion

2014-03-22 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=70920

Marek Olšák mar...@gmail.com changed:

   What|Removed |Added

Summary|[PIGLIT,radeonsi] SIGSEGV   |[GLSL compiler] SIGSEGV for
   |for |shaders/glsl-fs-inline-expl
   |shaders/glsl-fs-inline-expl |osion
   |osion   |

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev