From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 100618] Dead Island crash after starting a new game Date: Thu, 13 Apr 2017 04:06:16 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1176632258==" 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 E27CC6E7FB for ; Thu, 13 Apr 2017 04:06:15 +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 --===============1176632258== Content-Type: multipart/alternative; boundary="14920563750.0AEb5b.27660"; charset="UTF-8" --14920563750.0AEb5b.27660 Date: Thu, 13 Apr 2017 04:06:15 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D100618 --- Comment #11 from Michel D=C3=A4nzer --- (In reply to at46n from comment #10) > I started steam in a terminal but there is only steam and normal game out= put > like in crash.log but nothing from valgrind. It might be captured in ~/.steam/error.log . > And "valgrind --log-file=3Dval.txt %command%" doesn't give me a log file. Might try specifying an absolute path, or searching for val.txt inside ~/.steam/ . > But none the less Dead Island doesn't crash when started through valgrind= . I > can start a new game. That probably means there are indeed memory management/access violations, w= hich valgrind absorbs enough to make things limp along. So it would be good to s= ee the valgrind output. --=20 You are receiving this mail because: You are the assignee for the bug.= --14920563750.0AEb5b.27660 Date: Thu, 13 Apr 2017 04:06:15 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated

Comme= nt # 11 on bug 10061= 8 from Michel D=C3=A4nzer 
(In reply to at46n from comment #10)
> I started steam in a terminal but there is only =
steam and normal game output
> like in crash.log but nothing from valgrind.

It might be captured in ~/.steam/error.log .


> And "valgrind --log-file=3Dval.txt %command=
%" doesn't give me a log file.

Might try specifying an absolute path, or searching for val.txt inside
~/.steam/ .


> But none the less Dead Island doesn't crash when=
 started through valgrind. I
> can start a new game.

That probably means there are indeed memory management/access violations, w=
hich
valgrind absorbs enough to make things limp along. So it would be good to s=
ee
the valgrind output.

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