<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Segmentation fault in Gnome Shell when resuming from blank screen" href="https://bugs.freedesktop.org/show_bug.cgi?id=107520#c3">Comment # 3</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Segmentation fault in Gnome Shell when resuming from blank screen" href="https://bugs.freedesktop.org/show_bug.cgi?id=107520">bug 107520</a> from <a class="email" href="mailto:pbasista@gmail.com" title="Peter Bašista <pbasista@gmail.com>"> Peter Bašista</a> <pre>(In reply to Lionel Landwerlin from <a href="show_bug.cgi?id=107520#c1">comment #1</a>) > So far it has not ended up with a backtrace in mesa Then I believe that your issue is different. In my case, the crash always happens in mesa code. The last stack frame varies slightly, which is probably caused by wrong memory reference in the previous stack frame already. I have attached the most recent backtrace, where the topmost stack frame is unknown to the debugger, probably because the previous stack frame has already attempted to use wrong memory address. Not sure. As of how to debug this properly, I believe that a core dump may be sufficient for someone familiar with the code. I can provide a lot of them if needed. If there are too many optimized-out values to properly understand the issue, it would be necessary to compile some parts without optimizations and try again.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>