dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 91480] Dead Island: Crash loading Act 3 possible shader issue
Date: Mon, 27 Jul 2015 21:37:39 +0000	[thread overview]
Message-ID: <bug-91480-502-JYNpBVLkL6@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-91480-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 691 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=91480

--- Comment #2 from Ilia Mirkin <imirkin@alum.mit.edu> ---
FWIW I can't reproduce the segfault by running through glsl_compiler. I do,
however, get a

0:35(1): error: #extension directive is not allowed in the middle of a shader

But that should be work-around-able with a driconf setting (or by running the
game with allow_glsl_extension_directive_midshader=1 in the environment). When
I move the #extension line up, no complaints (other than the unknown
GL_ATI_draw_buffers thing), nothing in valgrind either.

Perhaps you can capture an apitrace of the issue?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1466 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2015-07-27 21:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-27 21:25 [Bug 91480] Dead Island: Crash loading Act 3 possible shader issue bugzilla-daemon
2015-07-27 21:26 ` bugzilla-daemon
2015-07-27 21:37 ` bugzilla-daemon [this message]
2015-07-28 20:29 ` bugzilla-daemon
2015-07-29 20:25 ` bugzilla-daemon
2016-04-19 12:08 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-91480-502-JYNpBVLkL6@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox