From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 64649] Anomaly 2 (Steam) exits with divide by 0 in r600g Date: Wed, 22 May 2013 15:00:40 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1056056697==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 1A767E63FF for ; Wed, 22 May 2013 08:00:41 -0700 (PDT) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org Errors-To: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============1056056697== Content-Type: multipart/alternative; boundary="1369234840.41f34C1.13546"; charset="us-ascii" --1369234840.41f34C1.13546 Date: Wed, 22 May 2013 15:00:40 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" https://bugs.freedesktop.org/show_bug.cgi?id=64649 --- Comment #16 from Kai --- (In reply to comment #15) > > 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? 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. -- You are receiving this mail because: You are the assignee for the bug. --1369234840.41f34C1.13546 Date: Wed, 22 May 2013 15:00:40 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8"

Comment # 16 on bug 64649 from
(In reply to comment #15)
> > 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?

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.


You are receiving this mail because:
  • You are the assignee for the bug.
--1369234840.41f34C1.13546-- --===============1056056697== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel --===============1056056697==--