dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 93352] GRID Autosport crashes on start of race
Date: Fri, 11 Dec 2015 17:27:53 +0000	[thread overview]
Message-ID: <bug-93352-502-88LLWT8lUw@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-93352-502@http.bugs.freedesktop.org/>


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

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

--- Comment #2 from Jürgen Scholz <juergen.scholz.84@gmail.com> ---
After installing (possibly unnecessary debug symbols and source files):
* aptitude install libgl1-mesa-dri-dev:i386 libgl1-mesa-dri-dbg:i386
libgl1-mesa-dri-dbg xserver-xorg-video-radeon-dbg libgl1-mesa-dev
* cd /usr/src; apt-get source libgl1-mesa-dri
* ln -s /usr/src/mesa-11.2~git151211033900.64c59b0~padoka0/src/mesa
/usr/src/mesa

The backtrace seems to be complete:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7f45137fe700 (LWP 9173)]
0x00007f452824cd43 in LLVMBuildLoad () from
/usr/lib/x86_64-linux-gnu/libLLVM-3.8.so.1
(gdb) bt
#0  0x00007f452824cd43 in LLVMBuildLoad () from
/usr/lib/x86_64-linux-gnu/libLLVM-3.8.so.1
#1  0x00007f452b751aa3 in emit_array_index (bld=<optimized out>, reg=<optimized
out>, offset=4294955456)
    at
../../../../../../src/gallium/drivers/radeon/radeon_setup_tgsi_llvm.c:108
#2  0x00007f452b753a25 in radeon_llvm_emit_fetch (bld_base=0x7f45137f57d0,
reg=0x7f43b7077f90, type=TGSI_TYPE_FLOAT, swizzle=0)
    at
../../../../../../src/gallium/drivers/radeon/radeon_setup_tgsi_llvm.c:191
#3  0x00007f452b4144e2 in lp_build_emit_fetch (bld_base=0x7f45137f57d0,
inst=0x7f43b7077f50, src_op=1, chan_index=<optimized out>)
    at ../../../../../src/gallium/auxiliary/gallivm/lp_bld_tgsi.c:351
#4  0x00007f452b414654 in lp_build_fetch_args (bld_base=0x7f45137f57d0,
emit_data=0x7f45137f4bd0) at
../../../../../src/gallium/auxiliary/gallivm/lp_bld_tgsi.c:180
#5  0x00007f452b4149db in lp_build_tgsi_inst_llvm (bld_base=0x7f45137f57d0,
inst=0x7f43b7077f50) at
../../../../../src/gallium/auxiliary/gallivm/lp_bld_tgsi.c:291
#6  0x00007f452b414c6d in lp_build_tgsi_llvm (bld_base=0x7f45137f57d0,
tokens=<optimized out>) at
../../../../../src/gallium/auxiliary/gallivm/lp_bld_tgsi.c:518
#7  0x00007f452b69161e in si_shader_create (sscreen=0x344fc20, tm=0x6a0fb30,
shader=0x7f43b6e51230)
    at ../../../../../../src/gallium/drivers/radeonsi/si_shader.c:4177
#8  0x00007f452b69c389 in si_shader_select (ctx=0x696cb30, state=0x696d780) at
../../../../../../src/gallium/drivers/radeonsi/si_state_shaders.c:619
#9  0x00007f452b69cd08 in si_update_shaders (sctx=0x696cb30) at
../../../../../../src/gallium/drivers/radeonsi/si_state_shaders.c:1514
#10 0x00007f452b699679 in si_draw_vbo (ctx=0x696cb30, info=0x7f45137fd300) at
../../../../../../src/gallium/drivers/radeonsi/si_state_draw.c:788
#11 0x00007f452b3ae207 in u_vbuf_draw_vbo (mgr=0x6a74200, info=0x7f45137fd300)
at ../../../../../src/gallium/auxiliary/util/u_vbuf.c:1162
#12 0x00007f452b1fa523 in st_draw_vbo (ctx=0x6a1ce70, prims=0x7f45137fd3c0,
nr_prims=<optimized out>, ib=0x0, index_bounds_valid=<optimized out>,
min_index=0,
    max_index=2, tfb_vertcount=0x0, stream=0, indirect=0x0) at
../../../../src/mesa/state_tracker/st_draw.c:291
#13 0x00007f452b1c83f6 in vbo_draw_arrays (ctx=0x6a1ce70, mode=14, start=0,
count=3, numInstances=1, baseInstance=0)
    at ../../../../src/mesa/vbo/vbo_exec_array.c:645
#14 0x00000000008b1171 in ?? ()
#15 0x00007f454205d030 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#16 0x00007f453cd2a6aa in start_thread (arg=0x7f45137fe700) at
pthread_create.c:333
#17 0x00007f453b52ceed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109
(gdb)

Can I supply more information?

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

[-- Attachment #1.2: Type: text/html, Size: 4317 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2015-12-11 17:27 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-11 16:44 [Bug 93352] GRID Autosport crashes on start of race bugzilla-daemon
2015-12-11 16:59 ` bugzilla-daemon
2015-12-11 17:27 ` bugzilla-daemon [this message]
2015-12-11 18:01 ` bugzilla-daemon
2015-12-11 19:38 ` bugzilla-daemon
2015-12-11 19:46 ` bugzilla-daemon
2015-12-11 20:20 ` bugzilla-daemon
2015-12-12  2:19 ` bugzilla-daemon
2015-12-12  2:35 ` bugzilla-daemon
2015-12-12  6:09 ` bugzilla-daemon
2015-12-12 12:44 ` bugzilla-daemon
2015-12-12 14:58 ` bugzilla-daemon
2015-12-13 16:11 ` bugzilla-daemon
2015-12-13 16:40 ` bugzilla-daemon
2015-12-14  0:57 ` bugzilla-daemon
2015-12-14  1:08 ` bugzilla-daemon
2015-12-14  1:37 ` bugzilla-daemon
2015-12-14  1:40 ` bugzilla-daemon
2015-12-14  7:17 ` bugzilla-daemon
2015-12-14  7:28 ` bugzilla-daemon
2015-12-14 10:13 ` bugzilla-daemon
2015-12-15 18:01 ` bugzilla-daemon
2015-12-26 21:04 ` bugzilla-daemon
2015-12-29 19:07 ` bugzilla-daemon
2016-01-16 18:34 ` bugzilla-daemon
2016-01-16 19:01 ` bugzilla-daemon
2016-01-16 19:05 ` bugzilla-daemon
2016-01-16 19:06 ` bugzilla-daemon
2016-01-16 19:27 ` bugzilla-daemon
2016-01-18  6: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-93352-502-88LLWT8lUw@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;
as well as URLs for NNTP newsgroup(s).