From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 96444] GRID Autosport crash on loading race Date: Sat, 11 Jun 2016 17:21:31 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1156263343==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [IPv6:2610:10:20:722:a800:ff:fe98:4b55]) by gabe.freedesktop.org (Postfix) with ESMTP id 0D2CD6E2C7 for ; Sat, 11 Jun 2016 17:21:31 +0000 (UTC) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============1156263343== Content-Type: multipart/alternative; boundary="14656656900.DBbeE88.2142"; charset="UTF-8" --14656656900.DBbeE88.2142 Date: Sat, 11 Jun 2016 17:21:30 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D96444 --- Comment #7 from Kai --- 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 comment #5) > (In reply to Nicolai H=C3=A4hnle from comment #3) > > No, you just need to provide a backtrace. Since you're running the game= via > > Steam, you could use `gdb -p ` after the game has started to attac= h 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; t= hen > > just use `bt full` to get a detailed backtrace. >=20 > 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 attachment 124477 looks suspiciously like you attached GDB to t= he 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 ga= me 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/SteamApp= s/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 4= 844, 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 i= ts 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 usu= ally setting in this case, so if you feel uncomfortable with reading a shell scr= ipt, don't do this. --=20 You are receiving this mail because: You are the assignee for the bug.= --14656656900.DBbeE88.2142 Date: Sat, 11 Jun 2016 17:21:30 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated

Comment= # 7 on bug 96444<= /a> from Kai
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 comme=
nt #5)
> (In reply to Nicolai H=C3=A4hnle from comment #3)
> > No, you just need to provide a backtrace. Since you're running th=
e game via
> > Steam, you could use `gdb -p <pid>` after the game has star=
ted to attach gdb
> > to the game. Once gdb has loaded, use `continue` to continue runn=
ing the
> > game. When it crashes, you should see a corresponding message in =
gdb; then
> > just use `bt full` to get a detailed backtrace.
>=20
> Sorry for the delay.
> I've tried to get a backtrace but I failed, don't know what I'm missin=
g.
> I've attached gdb log file.

Your log in attachment 124477 [details] 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 ga=
me
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/k=
ai/.local/share/Steam/SteamApps/common/The Talos Principle/Bin/x64/Talos&qu=
ot;
> 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 4=
844,
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 i=
ts
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 n=
ote, that you
might have to recreate the command line/environment the shell script is usu=
ally
setting in this case, so if you feel uncomfortable with reading a shell scr=
ipt,
don't do this.


You are receiving this mail because:
  • You are the assignee for the bug.
= --14656656900.DBbeE88.2142-- --===============1156263343== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============1156263343==--