From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 94984] XCom2 crashes with SIGSEGV on radeonsi Date: Mon, 18 Apr 2016 03:06:21 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0461322898==" 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 5C88C6E15F for ; Mon, 18 Apr 2016 03:06:21 +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 --===============0461322898== Content-Type: multipart/alternative; boundary="14609487810.5bf4b211F.28837"; charset="UTF-8" --14609487810.5bf4b211F.28837 Date: Mon, 18 Apr 2016 03:06:21 +0000 MIME-Version: 1.0 Content-Type: text/plain https://bugs.freedesktop.org/show_bug.cgi?id=94984 --- Comment #2 from Nicolai Hähnle --- Hi Moritz, thanks for the report. As for apitrace: In case you're running via Steam, consult this page: https://github.com/apitrace/apitrace/wiki/Steam - I've generally been successful with the instructions there. As to the bug itself: The immediate reason for the crash seems apparent enough: we fail to map the buffer into which query results are written. That code needs to be hardened, and I've added that on my todo list. However, we shouldn't fail that map in the first place. So an apitrace would indeed be helpful to understand better what's really going on here... do you have any other output from before the crash? -- You are receiving this mail because: You are the assignee for the bug. --14609487810.5bf4b211F.28837 Date: Mon, 18 Apr 2016 03:06:21 +0000 MIME-Version: 1.0 Content-Type: text/html

Comment # 2 on bug 94984 from 
Hi Moritz, thanks for the report.

As for apitrace: In case you're running via Steam, consult this page:
https://github.com/apitrace/apitrace/wiki/Steam - I've generally been
successful with the instructions there.

As to the bug itself: The immediate reason for the crash seems apparent enough:
we fail to map the buffer into which query results are written. That code needs
to be hardened, and I've added that on my todo list.

However, we shouldn't fail that map in the first place. So an apitrace would
indeed be helpful to understand better what's really going on here... do you
have any other output from before the crash?

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