From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 102009] Blender crashes when compiling OpenCL kernel
Date: Sun, 01 Oct 2017 15:58:16 +0000 [thread overview]
Message-ID: <bug-102009-502-29UaHBoOyM@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-102009-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 724 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=102009
--- Comment #7 from Markus <mw@graph-ix.net> ---
I tried to obtain debug information from Mesa but was unable to do so (i.e.
starting Blender with `MESA_DEBUG=context CYCLES_OPENCL_SPLIT_KERNEL_TEST=1
./blender` did not generate any visible debug information).
What I did instead, is run Blender via gdb which then gave the attached stack
trace at the time of crash. Looking at the trace, it appears like the crash is
inside LLVM.
What is the best way to debug this further?
P.S.: As I just updated to Ubuntu 17.10 (Beta 2), I've also attached new
glxinfo and clinfo output.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1487 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:[~2017-10-01 15:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-01 22:22 [Bug 102009] Blender crashes when compiling OpenCL kernel bugzilla-daemon
2017-08-01 22:23 ` bugzilla-daemon
2017-08-01 22:24 ` bugzilla-daemon
2017-08-01 22:44 ` bugzilla-daemon
2017-09-14 22:04 ` bugzilla-daemon
2017-10-01 15:47 ` bugzilla-daemon
2017-10-01 15:50 ` bugzilla-daemon
2017-10-01 15:50 ` bugzilla-daemon
2017-10-01 15:58 ` bugzilla-daemon [this message]
2017-11-14 23:23 ` bugzilla-daemon
2018-05-19 2:56 ` [Bug 102009] [clover, amdgcn] " bugzilla-daemon
2018-09-09 22:40 ` 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-102009-502-29UaHBoOyM@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