From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 95026] Alien Isolation segfault after initial loading screen/video
Date: Tue, 19 Apr 2016 22:34:06 +0000 [thread overview]
Message-ID: <bug-95026-502-1tMeMYhZvd@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-95026-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1206 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=95026
--- Comment #7 from Ilia Mirkin <imirkin@alum.mit.edu> ---
(In reply to Christoph Haag from comment #5)
> Created attachment 123072 [details]
> MESA_GLSL=dump with --enable-debug
>
> With CFLAGS and CXXFLAGS not set and --enable-debug, mesa is using this:
> CFLAGS: -g -O2 -Wall -std=c99 -Werror=implicit-function-declaration
> -Werror=missing-prototypes -fno-strict-aliasing -fno-math-errno
> -fno-trapping-math -fno-builtin-memcmp
> CXXFLAGS: -g -O2 -Wall -fno-strict-aliasing -fno-builtin-memcmp
>
> And the game crashes. Looks like +1 for O2.
Can you do "i threads" when it crashes? Are any other threads compiling shaders
at the same time?
It appears that the last linked fragment shader is from fragment shader 2749,
which is not the last glsl shader source to have been provided. Which is odd,
but not impossible. [Not 100% sure, but I think it's linked with vertex shader
2693.]
Need to run through through piglit and see what happens. However they look
simple enough. Could you poke around a bit more in gdb and see if there's
anything interesting?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2321 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-04-19 22:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-19 20:15 [Bug 95026] Alien Isolation segfault after initial loading screen/video bugzilla-daemon
2016-04-19 20:52 ` bugzilla-daemon
2016-04-19 21:00 ` bugzilla-daemon
2016-04-19 21:27 ` bugzilla-daemon
2016-04-19 21:37 ` bugzilla-daemon
2016-04-19 22:02 ` bugzilla-daemon
2016-04-19 22:31 ` bugzilla-daemon
2016-04-19 22:34 ` bugzilla-daemon [this message]
2016-04-19 22:52 ` bugzilla-daemon
2016-04-19 23:00 ` bugzilla-daemon
2016-04-19 23:01 ` bugzilla-daemon
2016-04-20 3:29 ` bugzilla-daemon
2016-04-20 7:27 ` bugzilla-daemon
2016-04-25 23:40 ` bugzilla-daemon
2016-04-26 10:07 ` bugzilla-daemon
2016-04-29 16:54 ` 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-95026-502-1tMeMYhZvd@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