From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 94242] [radeonsi] Crash while running Fedora mock tool for prompting root (gtksu)
Date: Fri, 26 Feb 2016 16:29:30 +0000 [thread overview]
Message-ID: <bug-94242-502-ONxe3q82tb@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-94242-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 472 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=94242
--- Comment #11 from Marek Olšák <maraeo@gmail.com> ---
The problematic shader is attached. It has "s_branch" at the end "ret"
somewhere in the middle. My initial theory is that the shader fails to jump to
the epilog, which is outside of the binary, and jumps somewhere else. It may be
even stuck in an infinite loop due to an incorrect jump.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1306 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-02-26 16:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-22 2:49 [Bug 94242] [radeonsi] Crash while running Fedora mock tool for prompting root (gtksu) bugzilla-daemon
2016-02-22 2:50 ` bugzilla-daemon
2016-02-22 7:04 ` bugzilla-daemon
2016-02-23 7:19 ` bugzilla-daemon
2016-02-23 15:39 ` bugzilla-daemon
2016-02-24 1:43 ` bugzilla-daemon
2016-02-25 16:55 ` bugzilla-daemon
2016-02-26 9:08 ` bugzilla-daemon
2016-02-26 11:20 ` bugzilla-daemon
2016-02-26 15:12 ` bugzilla-daemon
2016-02-26 16:21 ` bugzilla-daemon
2016-02-26 16:29 ` bugzilla-daemon [this message]
2016-03-07 6:02 ` bugzilla-daemon
2016-03-09 18:37 ` bugzilla-daemon
2016-03-10 17:02 ` bugzilla-daemon
2016-03-15 7:17 ` 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-94242-502-ONxe3q82tb@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