All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 94984] XCom2 crashes with SIGSEGV on radeonsi
Date: Thu, 21 Apr 2016 21:20:14 +0000	[thread overview]
Message-ID: <bug-94984-502-inV14tOE42@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-94984-502@http.bugs.freedesktop.org/>


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

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

--- Comment #6 from kuehner.moritz@gmail.com ---
So I was able to continue the game over the point of the crash on may laptop
and than save the game. This gives me a save game that crashes upon loading.

journald tells says this at the time of the crash:
OpenGL dispatch[7562]: segfault at 0 ip 00007fef119622ce sp 00007fee95ffa368
error 6 in libc-2.23.so[7fef117f0000+1c0000]

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

[-- Attachment #1.2: Type: text/html, Size: 1237 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:[~2016-04-21 21:20 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-17 20:00 [Bug 94984] XCom2 crashes with SIGSEGV on radeonsi bugzilla-daemon
2016-04-17 20:01 ` bugzilla-daemon
2016-04-18  3:06 ` bugzilla-daemon
2016-04-18 19:05 ` bugzilla-daemon
2016-04-21 13:04 ` bugzilla-daemon
2016-04-21 21:18 ` bugzilla-daemon
2016-04-21 21:20 ` bugzilla-daemon [this message]
2016-04-22  7:40 ` bugzilla-daemon
2016-04-22  9:02 ` bugzilla-daemon
2016-04-22 23:51 ` bugzilla-daemon
2016-04-23  2:53 ` bugzilla-daemon
2016-04-23  3:38 ` bugzilla-daemon
2016-04-25  8:30 ` bugzilla-daemon
2016-09-22 11:23 ` bugzilla-daemon
2016-09-27 10:19 ` bugzilla-daemon
2016-09-27 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-94984-502-inV14tOE42@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.