Issues with proton/wine games

[korcankaraokcu]

After a breakpoint hits, it becomes impossible to stop the process again with the interrupt command. Unfortunately, this is a GDB bug so there's not much we can do. Rest of the features work fine, you can still search the memory etc. However, you only got one shot with the debugger so use it wisely :D

[korcankaraokcu]

Created a bug entry for this one, hopefully it'll get fixed
https://sourceware.org/bugzilla/show_bug.cgi?id=31359

[Bloodiko]

Adding to this:

No sure if generally applicable, but i just did some tests on 64 bit games, which were way more resilient toward the issue.
Using breakpoint once did not break gdb, but the issue still arose at some point. not exactly sure what else triggers it.

[korcankaraokcu]

Apparently we have a workaround for this one! If you notice that your process becomes unable to be stopped, just start a short trace session and GDB will be able to stop the process again

You can start a trace session by following these steps:

• Open the memory view
• In the disassembler, right click on the address where your last instruction pointer was pointing at and choose "Break and Trace"
• If the step above doesn't work, you can execute break command within the GDB Console (top right in the main menu) and then try step 2 again
• After the trace session ends, the issue should be fixed

A similar issue also exists in #261

[brkzlr]

Recently we started seeing GDB crashes upon WINE/Proton games attach so there is something funky going on with GDB.
Hopefully this will be auto-fixed when and if we move to LLDB.

[korcankaraokcu]

Locked the issue to use it for tracking purposes, you can freely reference this issue in other issues. We'll add it here if it's something useful