dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 100618] Dead Island crash after starting a new game
Date: Wed, 12 Apr 2017 15:35:09 +0000	[thread overview]
Message-ID: <bug-100618-502-UmrGFMa1z0@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-100618-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 965 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=100618

--- Comment #10 from at46n@t-online.de ---
Yes, that works. Valgrind starts the game which takes a long time (about 20
min). But how do I get the log from valgrind now? I started steam in a terminal
but there is only steam and normal game output like in crash.log but nothing
from valgrind. I also tried starting steam with "steam > log.txt 2>&1" but
there's nothing from valgrind in log.txt either. And "valgrind
--log-file=val.txt %command%" doesn't give me a log file.
But none the less Dead Island doesn't crash when started through valgrind. I
can start a new game. Unfortunately the character spawns somewhere out of the
map and dies, repeatable. But I couldn't get the game to crash any more. If I
start the game without valgrind it crashes either from a new game or from
continuing the game started in valgrind.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1743 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2017-04-12 15:35 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-08 10:20 [Bug 100618] Dead Island bugzilla-daemon
2017-04-08 10:22 ` [Bug 100618] Dead Island crash after starting a new game bugzilla-daemon
2017-04-08 10:25 ` bugzilla-daemon
2017-04-10  3:19 ` bugzilla-daemon
2017-04-10  6:43 ` bugzilla-daemon
2017-04-10  6:49 ` bugzilla-daemon
2017-04-10  6:58 ` bugzilla-daemon
2017-04-10 14:55 ` bugzilla-daemon
2017-04-10 15:34 ` bugzilla-daemon
2017-04-11  2:07 ` bugzilla-daemon
2017-04-11 15:37 ` bugzilla-daemon
2017-04-12  1:50 ` bugzilla-daemon
2017-04-12 15:35 ` bugzilla-daemon [this message]
2017-04-13  4:06 ` bugzilla-daemon
2017-04-13 15:58 ` bugzilla-daemon
2017-05-09 17:47 ` bugzilla-daemon
2017-05-09 18:30 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-100618-502-UmrGFMa1z0@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox