Comment=
# 3
on bug 92850<=
/a>
from Nicolai H=C3=A4hnle
Backtrace: When running in gdb, enter the "bt" comma=
nd 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 distributi=
on
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 it=
self
(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 thi=
s.
_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. General=
ly,
using such overrides pretty much means all bets are off.