From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 74868] r600g: Diablo III Crashes After a few minutes Date: Sun, 16 Feb 2014 04:15:30 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0599510971==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 7CF89FA3F7 for ; Sat, 15 Feb 2014 20:15:30 -0800 (PST) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dri-devel-bounces@lists.freedesktop.org Errors-To: dri-devel-bounces@lists.freedesktop.org To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============0599510971== Content-Type: multipart/alternative; boundary="1392524130.07Fc20.32200"; charset="us-ascii" --1392524130.07Fc20.32200 Date: Sun, 16 Feb 2014 04:15:30 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" https://bugs.freedesktop.org/show_bug.cgi?id=74868 --- Comment #8 from Ilia Mirkin --- (In reply to comment #7) > Created attachment 94142 [details] > Diablo III Valgrind output > > Thanks Ilia, that did the trick! I just grabbed the first few minutes of > game play in Valgrind up until it started encountering the error that was > popping previously. I'm not a radeon guy, just a drive-by commenter, but I'm going to go ahead and guess that this output is going to be of little use to anyone debugging :( A trace with symbols in r600_dri would be much more useful. With what you provided, we just know that the memory is allocated with malloc and calloc... which is of little surprise. -- You are receiving this mail because: You are the assignee for the bug. --1392524130.07Fc20.32200 Date: Sun, 16 Feb 2014 04:15:30 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8"

Comment # 8 on bug 74868 from 
(In reply to comment #7)
> Created attachment 94142 [details]
> Diablo III Valgrind output
> 
> Thanks Ilia, that did the trick! I just grabbed the first few minutes of
> game play in Valgrind up until it started encountering the error that was
> popping previously.

I'm not a radeon guy, just a drive-by commenter, but I'm going to go ahead and
guess that this output is going to be of little use to anyone debugging :(

A trace with symbols in r600_dri would be much more useful. With what you
provided, we just know that the memory is allocated with malloc and calloc...
which is of little surprise.

You are receiving this mail because:
  • You are the assignee for the bug.
--1392524130.07Fc20.32200-- --===============0599510971== 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 --===============0599510971==--