<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - r600g: Diablo III Crashes After a few minutes" href="https://bugs.freedesktop.org/show_bug.cgi?id=74868#c8">Comment # 8</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - r600g: Diablo III Crashes After a few minutes" href="https://bugs.freedesktop.org/show_bug.cgi?id=74868">bug 74868</a> from <a class="email" href="mailto:imirkin@alum.mit.edu" title="Ilia Mirkin <imirkin@alum.mit.edu>"> Ilia Mirkin</a> <pre>(In reply to <a href="show_bug.cgi?id=74868#c7">comment #7</a>) > Created <a href="attachment.cgi?id=94142" name="attach_94142" title="Diablo III Valgrind output">attachment 94142</a> <a href="attachment.cgi?id=94142&action=edit" title="Diablo III Valgrind output">[details]</a> > 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.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>