[Bug 92850] Segfault loading War Thunder

[bugzilla-daemon@freedesktop.org]

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

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

--- Comment #3 from Nicolai Hähnle <nhaehnle@gmail.com> ---
Backtrace: When running in gdb, enter the "bt" command after the crash. That
will give you the backtrace.

Debug symbols: If you compile Mesa yourself, I believe running the configure
script with --enable-debug in addition to the other usual options and
recompiling everything should do the trick. If you're using some distribution
package, there should usually be packages with a -dbg name that will install
the required debug symbols.

Apitrace: Even if apitrace does not give you an error message, the trace itself
(i.e. the generated .trace file) could be useful for reproducing the issue. Zip
it (xz is popular) and upload it somewhere if possible.

Also, please provide the full output of glxinfo and dmesg for bugs like this.

_However_, even with all that said, it is entirely possible that the version
override is messing something up. If other people have been using Mesa with the
override successfully, they might have other hardware and just been lucky
enough to be using a driver that happens to work with the override. Generally,
using such overrides pretty much means all bets are off.

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

[-- Attachment #1.2: Type: text/html, Size: 2072 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