<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - Anomaly 2 (Steam) exits with divide by 0 in r600g"
href="https://bugs.freedesktop.org/show_bug.cgi?id=64649#c16">Comment # 16</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW --- - Anomaly 2 (Steam) exits with divide by 0 in r600g"
href="https://bugs.freedesktop.org/show_bug.cgi?id=64649">bug 64649</a>
from <span class="vcard"><a class="email" href="mailto:kai@dev.carbon-project.org" title="Kai <kai@dev.carbon-project.org>"> <span class="fn">Kai</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=64649#c15">comment #15</a>)
<span class="quote">> > Again, just to make sure you don't search for a bug that is maybe no longer
> > in r600g: I don't have the latest master for Mesa/libdrm, and it'll take me
> > at least a few days, before I can get around to build a new version. Hency
> > you might want to confirm the backtrace with somebody who runs master.
>
> I will the backtrace, could you give me the exact command you used?</span >
The command is
gdb "~/.local/share/Steam/SteamApps/common/Anomaly 2/Anomaly2Linux" [ProcID]
but that alone isn't enough. First you need to install the debugging symbols
for Mesa and libc (the 32 bit versions!). Then you need to start Steam and
Anomaly 2 through Steam. While the intro is playing you need to tab to a
console, determine the process ID (with ps) and then replace [ProcID] in the
command above. After gdb has attached itself to Anomaly 2, you will see the gdb
prompt where you need to type c (or continue). After that, you can tab back to
the game and wait until you hit the crash. Then you should be back to your
desktop (and console windows). There you have to type in
bt full
and
info registers
You can exit gdb (and the attached Anomaly 2) by typing in q (or quit).
If you want to redirect the output of the above commands to a file, use
set logging file /path/to/log-file
set logging on
before you type c (or continue).
If you have trouble getting through all commands before the intro ends, you
might want to prepare them beforehand.
I hope this helps.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>