From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 92850] Segfault loading War Thunder
Date: Tue, 01 Dec 2015 17:33:50 +0000 [thread overview]
Message-ID: <bug-92850-502-gujQMQRMJG@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-92850-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1499 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=92850
haro41@gmx.de changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |haro41@gmx.de
--- Comment #23 from haro41@gmx.de ---
I have a similiar segmentation fault error in game 'war thunder' (mesa
11.2-devel radeonsi). Unlike the original reporter, i dont use/need any GL
version override.
If i configure latest git mesa with '--enable-debug', i get this additional
output at console, before the crash:
'context mis-match in pipe_sampler_view_release()'
glxinfo |grep OpenGL:
OpenGL vendor string: X.Org
OpenGL renderer string: Gallium 0.4 on AMD PITCAIRN (DRM 2.43.0, LLVM 3.7.0)
OpenGL core profile version string: 4.1 (Core Profile) Mesa 11.2.0-devel
(git-241f15a)
OpenGL core profile shading language version string: 4.10
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 3.0 Mesa 11.2.0-devel (git-241f15a)
OpenGL shading language version string: 1.30
OpenGL context flags: (none)
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.0 Mesa 11.2.0-devel (git-241f15a)
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00
OpenGL ES profile extensions:
If additinal infos are needed please let me know.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2671 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
next prev parent reply other threads:[~2015-12-01 17:33 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-06 21:36 [Bug 92850] Segfault loading War Thunder bugzilla-daemon
2015-11-07 10:52 ` bugzilla-daemon
2015-11-07 14:52 ` bugzilla-daemon
2015-11-07 19:41 ` bugzilla-daemon
2015-11-11 4:22 ` bugzilla-daemon
2015-11-11 15:09 ` bugzilla-daemon
2015-11-11 17:36 ` bugzilla-daemon
2015-11-11 17:37 ` bugzilla-daemon
2015-11-12 9:32 ` bugzilla-daemon
2015-11-12 14:41 ` bugzilla-daemon
2015-11-12 14:45 ` bugzilla-daemon
2015-11-12 14:49 ` bugzilla-daemon
2015-11-20 23:27 ` bugzilla-daemon
2015-11-23 8:34 ` bugzilla-daemon
2015-11-23 15:56 ` bugzilla-daemon
2015-11-24 10:16 ` bugzilla-daemon
2015-11-24 19:28 ` bugzilla-daemon
2015-11-24 19:29 ` bugzilla-daemon
2015-11-24 19:43 ` bugzilla-daemon
2015-11-26 17:13 ` bugzilla-daemon
2015-11-27 16:44 ` bugzilla-daemon
2015-11-27 19:21 ` bugzilla-daemon
2015-11-30 22:08 ` bugzilla-daemon
2015-12-01 17:33 ` bugzilla-daemon [this message]
2015-12-02 15:29 ` bugzilla-daemon
2015-12-02 17:46 ` bugzilla-daemon
2015-12-02 17:47 ` bugzilla-daemon
2015-12-03 1:14 ` bugzilla-daemon
2015-12-03 1:25 ` 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-92850-502-gujQMQRMJG@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