Hello @abelbriggs1, adding PROTON_DUMP_DEBUG_COMMANDS=1 %command% to a game's launch options, then running the game adds a some convenience scripts to /tmp/proton_<username>/, including winedbg_run, which sounds like the script you're looking for.
Hello @abelbriggs1, adding
PROTON_DUMP_DEBUG_COMMANDS=1 %command%to a game's launch options, then running the game adds a some convenience scripts to/tmp/proton_<username>/, includingwinedbg_run, which sounds like the script you're looking for.
Thanks, that's exactly what I was looking for and it works perfectly. I must have missed that when looking at launch options.
If possible will be cool if someone write this in the FAQ, I don't found many results too about debugging.
Trying to debug a game, i only get:
Can't attach process 000a: error 87
syntax error
proton 4.11x1 2020-01PROTON_DUMP_DEBUG_COMMANDS=1x2 2020-01
Hi,
I'm trying to attach the Wine debugger to Proton so I can look into a game's code during runtime.
When I run winedbg, the
info processcommand does not contain the game process that I'm trying to look into. For example:This happens regardless of whether I run the Proton 4.11 winedbg or my normal Wine installation winedbg.
I've searched around for a few hours through the issue tracker and though I've found plenty of evidence of people looking into Proton games with winedbg, I've been completely unable to find any documentation of how they did so. Indeed, the closest I came was finding someone who had a similar problem trying to debug with winedbg. However, their issue was solved without the need for that information.
Additionally, I've seen references to a "proton_winedbg_run" script which I imagine does what I want, but it seems to be non-existent in my Proton installation.
Any help would be appreciated. Thanks.