<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - Using SB shader optimization caused segfault in Serious Sam 3: BFE" href="https://bugs.freedesktop.org/show_bug.cgi?id=66349#c3">Comment # 3</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - Using SB shader optimization caused segfault in Serious Sam 3: BFE" href="https://bugs.freedesktop.org/show_bug.cgi?id=66349">bug 66349</a> from <a class="email" href="mailto:ptpzz@yandex.ru" title="Vadim Girlin <ptpzz@yandex.ru>"> Vadim Girlin</a> <pre>(In reply to <a href="show_bug.cgi?id=66349#c2">comment #2</a>) > Created <a href="attachment.cgi?id=81982" name="attach_81982" title="output with R600_DEBUG=sb,ps,vs">attachment 81982</a> <a href="attachment.cgi?id=81982&action=edit" title="output with R600_DEBUG=sb,ps,vs">[details]</a> > output with R600_DEBUG=sb,ps,vs > > Steam also use opengl to draw it's UI so some of these shaders comes from it. Steam shaders are not a problem, I'm mostly interested in the last shader that causes the crash. Unfortunately, I can't reproduce it, for me sb handles that shader without any problems. Please make sure that the game actually uses the latest mesa from git (AFAICS the app is 32-bit so it uses 32-bit mesa). Possibly there is some weird issue like memory corruption, does it always happen at the same point (same backtrace, same last shader in the dump)? You might want to try running the app with debug build of mesa (configured with --enable-debug), it can provide some additional info if the issue can be caught by asserts, and better backtrace. Could you also try to record a trace using apitrace (without sb) and then check if issue is reproducible when the trace is replayed with sb. If it will be reproducible, then hopefully I'll be able to reproduce it on my system too.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>