Skip to content
Snippets Groups Projects
Commit 823c80cc authored by Simon McVittie's avatar Simon McVittie
Browse files

launch-client(1): Move the gdbserver example up to the SLR 3.0 section


Using gdbserver is a piece of complexity that is orthogonal to either
SLR 1.0 or Proton.

Signed-off-by: default avatarSimon McVittie <smcv@collabora.com>
parent 39ba0459
No related branches found
No related tags found
No related merge requests found
......@@ -471,6 +471,25 @@ in this example **wflinfo**(1):
that will run successfully inside the container,
for example `steam-runtime-system-info`, `xterm` or `bash -i`.
The same mechanism can be used to attach an interactive debugger,
with commands like:
$ steam-runtime-launch-client --list
--bus-name=com.steampowered.App440
--bus-name=com.steampowered.App440.Instance54321
$ pgrep hl2_linux
12345
$ gdb ./hl2_linux
(gdb) set sysroot /proc/12345/root
(gdb) target remote | \
steam-runtime-launch-client \
--bus-name=com.steampowered.App440 \
-- gdbserver --attach - 12345
(gdb) thread apply all bt
(gdb) detach
For a Steam game that runs under the "Steam Linux Runtime 1.0 (scout)"
compatibility tool, the procedure is similar, but you would usually set
its Steam Launch Options to
......@@ -497,30 +516,6 @@ like:
-- \
wine winedbg notepad.exe
Similarly, for a Steam game that runs under the
"Steam Linux Runtime 1.0 (scout)"
compatibility tool, if you set its Steam Launch Options to
STEAM_COMPAT_LAUNCHER_SERVICE=scout-in-container %command%
then you can attach a debugger with commands like:
$ steam-runtime-launch-client --list
--bus-name=com.steampowered.App440
--bus-name=com.steampowered.App440.Instance54321
$ pgrep hl2_linux
12345
$ gdb ./hl2_linux
(gdb) set sysroot /proc/12345/root
(gdb) target remote | \
steam-runtime-launch-client \
--bus-name=com.steampowered.App440 \
-- gdbserver --attach - 12345
(gdb) thread apply all bt
(gdb) detach
If a game is crashing on startup, this can be debugged by setting its
Steam Launch Options to
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment