<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - XCOM: Enemy Unknown Causes lockup" href="https://bugs.freedesktop.org/show_bug.cgi?id=80419#c85">Comment # 85</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - XCOM: Enemy Unknown Causes lockup" href="https://bugs.freedesktop.org/show_bug.cgi?id=80419">bug 80419</a> from <a class="email" href="mailto:kamil.paral@gmail.com" title="Kamil Páral <kamil.paral@gmail.com>"> Kamil Páral</a> <pre>(In reply to Daniel Exner from <a href="show_bug.cgi?id=80419#c80">comment #80</a>) > Now I get (with radeonsi): > > glretrace game.x86_64.trace > apitrace: warning: caught signal 11 > 47062: error: caught an unhandled exception Great to see it does not crash just for me :-) (In reply to Michael Eagle from <a href="show_bug.cgi?id=80419#c82">comment #82</a>) > On Fedora 23 I'm using this copr: > <a href="https://copr.fedoraproject.org/coprs/griever/mesa-git/">https://copr.fedoraproject.org/coprs/griever/mesa-git/</a> Thanks, that helps a lot! (In reply to Daniel Exner from <a href="show_bug.cgi?id=80419#c83">comment #83</a>) > Managed to get some more infos about glretrace crash: Please note I uploaded a gdb backtrace to the apitrace bug mentioned in <a href="show_bug.cgi?id=80419#c73">comment 73</a>. Now that I tested latest mesa git (ea8c0b1, 2012-12-21), I can confirm apitrace still crashes, and I uploaded an updated gdb backtrace: <a href="https://github.com/apitrace/apitrace/files/69636/gdb.backtrace2.txt">https://github.com/apitrace/apitrace/files/69636/gdb.backtrace2.txt</a> However, the question is whether that apitrace crash is related to the gpu hang we see in XCOM. It certainly makes debugging harder.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>