From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 96678] Awesomenauts cannot launch AMD PITCAIRN
Date: Wed, 06 Jul 2016 09:21:29 +0000 [thread overview]
Message-ID: <bug-96678-502-icdurpH2zY@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-96678-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1017 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=96678
--- Comment #9 from Nicolai Hähnle <nhaehnle@gmail.com> ---
Thanks.
The crash happens inside the implementation of std::stable_sort when called
from LLVM. An internal buffer pointer seems to be corrupted. Since the buffer
pointer lives on the stack I don't have a good explanation for this, just some
hypotheses we can follow up on:
1. Joost, does Awesomenauts do anything non-standard when linking to libstdc++?
Perhaps symbols get mixed up in a way that leads to the wrong code being
executed. It wouldn't be the first time that problems come from there, although
usually when games do that they just fail to load in the dynamic linker.
2. Quentin, you could try running the game with Valgrind and see if anything
comes up. It's going to be slow, but if there is a stack-smashing bug here in
LLVM (extremely unlikely, but whatever) then Valgrind should catch it.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1780 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
next prev parent reply other threads:[~2016-07-06 9:21 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-26 1:46 [Bug 96678] Awesomenauts cannot launch AMD PITCAIRN bugzilla-daemon
2016-07-01 13:13 ` bugzilla-daemon
2016-07-04 2:33 ` bugzilla-daemon
2016-07-04 2:34 ` bugzilla-daemon
2016-07-04 2:50 ` bugzilla-daemon
2016-07-04 2:51 ` bugzilla-daemon
2016-07-04 10:16 ` bugzilla-daemon
2016-07-04 16:00 ` bugzilla-daemon
2016-07-05 2:03 ` bugzilla-daemon
2016-07-06 9:21 ` bugzilla-daemon [this message]
2016-07-06 9:42 ` bugzilla-daemon
2016-07-06 10:43 ` bugzilla-daemon
2016-07-06 10:46 ` bugzilla-daemon
2016-07-06 12:16 ` bugzilla-daemon
2016-07-06 12:45 ` bugzilla-daemon
2016-07-06 12:50 ` bugzilla-daemon
2016-07-06 13:01 ` bugzilla-daemon
2016-07-07 3:06 ` bugzilla-daemon
2016-07-07 6:51 ` bugzilla-daemon
2016-07-07 6:54 ` bugzilla-daemon
2016-07-07 7:50 ` bugzilla-daemon
2016-07-07 9:44 ` bugzilla-daemon
2016-07-07 13:03 ` bugzilla-daemon
2016-07-07 13:29 ` bugzilla-daemon
2016-07-13 9:26 ` bugzilla-daemon
2016-07-23 11:16 ` bugzilla-daemon
2016-07-23 11:31 ` bugzilla-daemon
2016-10-26 10:51 ` bugzilla-daemon
2016-10-27 5:47 ` bugzilla-daemon
2016-11-04 10:15 ` 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-96678-502-icdurpH2zY@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.