https://bugs.freedesktop.org/show_bug.cgi?id=100618
--- Comment #14 from John Brooks ---
(In reply to at46n from comment #13)
> Seems like its a glsl compiler bug and not a radeonsi bug. With "prlimit
> --pid PIDofDeadIsland -n65535" I am able to start and play
https://bugs.freedesktop.org/show_bug.cgi?id=100618
at...@t-online.de changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=100618
--- Comment #12 from at...@t-online.de ---
Created attachment 130831
--> https://bugs.freedesktop.org/attachment.cgi?id=130831=edit
valgrind logfile
An absolute path was the key. Logfile from valgrind is attached.
--
You are receiving this
https://bugs.freedesktop.org/show_bug.cgi?id=100618
--- Comment #11 from Michel Dänzer ---
(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
https://bugs.freedesktop.org/show_bug.cgi?id=100618
--- Comment #10 from at...@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
https://bugs.freedesktop.org/show_bug.cgi?id=100618
--- Comment #9 from Michel Dänzer ---
Something like
valgrind %command%
in the game's Properties -> Launch Options should work.
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=100618
--- Comment #8 from at...@t-online.de ---
I have no idea how to start the game in valgrind because I have to start the
game through steam. For gdb I used the --pid option to take over the process of
the game after starting it through steam but
https://bugs.freedesktop.org/show_bug.cgi?id=100618
--- Comment #7 from Michel Dänzer ---
That's it, thanks.
There is no direct reference to any driver code in the backtrace. It's still
possible that the crash is at least indirectly related to driver code, but the
backtrace
https://bugs.freedesktop.org/show_bug.cgi?id=100618
at...@t-online.de changed:
What|Removed |Added
Attachment #130779|0 |1
is obsolete|
https://bugs.freedesktop.org/show_bug.cgi?id=100618
--- Comment #5 from at...@t-online.de ---
Created attachment 130779
--> https://bugs.freedesktop.org/attachment.cgi?id=130779=edit
gdb backtrace after crash
I'm not familiar with gdb, so I'm not sure if I did what you were asking for. I
https://bugs.freedesktop.org/show_bug.cgi?id=100618
--- Comment #4 from Michel Dänzer ---
Can you try attaching gdb to the game process and getting a backtrace of the
crash?
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=100618
--- Comment #3 from at...@t-online.de ---
I added the crash log of the game. There is no error at the end. The Game seems
to crash while compiling shaders. Let me know if I could do any more to help
with this bug or if you need more infos of my
https://bugs.freedesktop.org/show_bug.cgi?id=100618
--- Comment #2 from at...@t-online.de ---
Created attachment 130769
--> https://bugs.freedesktop.org/attachment.cgi?id=130769=edit
crash log of Dead Island
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=100618
--- Comment #1 from Michel Dänzer ---
What are the symptoms of the crash? Can you get a backtrace?
--
You are receiving this mail because:
You are the assignee for the bug.___
https://bugs.freedesktop.org/show_bug.cgi?id=100618
at...@t-online.de changed:
What|Removed |Added
See Also||https://bugs.freedesktop.or
https://bugs.freedesktop.org/show_bug.cgi?id=100618
at...@t-online.de changed:
What|Removed |Added
Summary|Dead Island |Dead Island crash after
16 matches
Mail list logo