<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - GRID Autosport crash on loading race" href="https://bugs.freedesktop.org/show_bug.cgi?id=96444#c7">Comment # 7</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - GRID Autosport crash on loading race" href="https://bugs.freedesktop.org/show_bug.cgi?id=96444">bug 96444</a> from <a class="email" href="mailto:kai@dev.carbon-project.org" title="Kai <kai@dev.carbon-project.org>"> Kai</a> <pre>Hey Lorenzo, I can't weigh in on GRID, but I can give you some pointers with your GDB troubles. (In reply to Lorenzo Bona from <a href="show_bug.cgi?id=96444#c5">comment #5</a>) > (In reply to Nicolai Hähnle from <a href="show_bug.cgi?id=96444#c3">comment #3</a>) > > No, you just need to provide a backtrace. Since you're running the game via > > Steam, you could use `gdb -p <pid>` after the game has started to attach gdb > > to the game. Once gdb has loaded, use `continue` to continue running the > > game. When it crashes, you should see a corresponding message in gdb; then > > just use `bt full` to get a detailed backtrace. > > Sorry for the delay. > I've tried to get a backtrace but I failed, don't know what I'm missing. > I've attached gdb log file. Your log in <a href="attachment.cgi?id=124477" name="attach_124477" title="gdb log">attachment 124477</a> <a href="attachment.cgi?id=124477&action=edit" title="gdb log">[details]</a> looks suspiciously like you attached GDB to the shell script launching the actual binary of the game. You need to attach to the game itself. grep the output of ps once you've launched the game for that name of the game to find the right process to attach to. Since the shell is launched right before the actual game, you'll often find the next PID after the shell to be the game. For The Talos Principle it just looked like this: $ ps a | grep -i talos > 4843 pts/13 S+ 0:00 /bin/sh -c "/home/kai/.local/share/Steam/SteamApps/common/The Talos Principle/Bin/x64/Talos" > 4844 pts/13 Rl+ 0:19 /home/kai/.local/share/Steam/SteamApps/common/The Talos Principle/Bin/x64/Talos As you can see, there are two processes and I would need to attach GDP to 4844, the first is the shell launching the game (in this case directly, but again, there are some games which have their own launcher script/launcher that launches the actual game, if you're unsure what the actual binary is, check the game folder in $HOME/.local/share/Steam/SteamApps/common). Depending on the game you could also try to launch the game directly from its folder with GDB. For this to work you need to add a steam_appid.txt to the top level of the game folder with the App ID as its content for most games. (The easiest way to find the ID is to check the store URL for your game. Then numeric value after "/app/" is what you're looking for). Please note, that you might have to recreate the command line/environment the shell script is usually setting in this case, so if you feel uncomfortable with reading a shell script, don't do this.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>