From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 29901] New: [r300g] Programs crash with segfault
Date: Tue, 31 Aug 2010 02:14:59 -0700 (PDT) [thread overview]
Message-ID: <bug-29901-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=29901
Summary: [r300g] Programs crash with segfault
Product: Mesa
Version: git
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: major
Priority: medium
Component: Drivers/DRI/r300
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: ncl@privat.dk
In the last week a lot of my program crash with a segfault (OpenSceneGraph,
Blender 2.5.3, Make Human etc.). Other program with gallium works ok. They all
crash the same way and here are my (gdb) bt:
Program received signal SIGSEGV, Segmentation fault.
#0 0x00007fffe52fd130 in r300_emit_aos_swtcl (r300=0xfceb40, indexed=0 '\000')
at r300_emit.c:847
#1 0x00007fffe52fec13 in r300_render_draw_arrays (render=0xb01750,
start=<value optimised out>, count=4) at r300_render.c:834
#2 0x00007fffe54bb52b in draw_pt_emit_linear (emit=<value optimised out>,
vert_info=<value optimised out>, prim_info=0x7fffffff9930) at
draw/draw_pt_emit.c:265
#3 0x00007fffe54ba49e in emit (middle=0xa69800, fetch_info=0x7fffffff9960,
prim_info=0x7fffffff9930) at draw/draw_pt_fetch_shade_pipeline_llvm.c:200
#4 llvm_pipeline_generic (middle=0xa69800, fetch_info=0x7fffffff9960,
prim_info=0x7fffffff9930) at draw/draw_pt_fetch_shade_pipeline_llvm.c:288
#5 0x00007fffe54ba5a4 in llvm_middle_end_linear_run (middle=0xc7, start=<value
optimised out>, count=4, prim_flags=201) at
draw/draw_pt_fetch_shade_pipeline_llvm.c:348
#6 0x00007fffe5479981 in vsplit_segment_simple_linear (frontend=0xff60c0,
start=368, count=4) at draw/draw_pt_vsplit_tmp.h:229
#7 vsplit_run_linear (frontend=0xff60c0, start=368, count=4) at
draw/draw_split_tmp.h:61
#8 0x00007fffe5475ba5 in draw_pt_arrays (draw=0xfe1570, info=0x7fffffffa170)
at draw/draw_pt.c:113
#9 draw_vbo (draw=0xfe1570, info=0x7fffffffa170) at draw/draw_pt.c:398
#10 0x00007fffe52ffc86 in r300_swtcl_draw_vbo (pipe=0xfceb40,
info=0x7fffffffa170) at r300_render.c:687
#11 0x00007fffe5430b8b in st_draw_vbo (ctx=<value optimised out>, arrays=<value
optimised out>, prims=<value optimised out>, nr_prims=<value optimised out>,
ib=0x0, index_bounds_valid=<value optimised out>, min_index=0, max_index=511)
at state_tracker/st_draw.c:722
#12 0x00007fffe5454588 in vbo_save_playback_vertex_list (ctx=0x100cc20,
data=0xe178b0) at vbo/vbo_save_draw.c:287
#13 0x00007fffe5340d7a in ext_opcode_execute (ctx=0x100cc20, list=<value
optimised out>) at main/dlist.c:533
#14 execute_list (ctx=0x100cc20, list=<value optimised out>) at
main/dlist.c:6883
#15 0x00007fffe5343922 in _mesa_CallList (list=3) at main/dlist.c:8140
My system: Radeon 1250x (rs600), ubuntu maverick 10.10 64 bit, running mesa
from xorg-edgers fresh X crack (mesa from 30/8/2010).
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2010-08-31 9:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-31 9:14 bugzilla-daemon [this message]
2010-09-06 3:35 ` [Bug 29901] [r300g] Programs crash with segfault bugzilla-daemon
2010-09-06 3:36 ` bugzilla-daemon
2010-09-06 3:41 ` [Bug 29901] [r300g] Commit eb430b0e948caf02b9f4095d0e1435880073c2aa breaks swtcl bugzilla-daemon
2010-09-06 22:33 ` bugzilla-daemon
2010-09-09 23:41 ` bugzilla-daemon
2010-09-10 22:13 ` bugzilla-daemon
2010-09-13 11:30 ` bugzilla-daemon
2010-09-14 16:57 ` [Bug 29901] [r300g] emit_aos_swtcl crash bugzilla-daemon
2010-09-15 3:26 ` bugzilla-daemon
2010-09-15 12:52 ` bugzilla-daemon
2010-09-16 0:10 ` bugzilla-daemon
2010-09-16 3:00 ` bugzilla-daemon
2010-09-16 10:01 ` bugzilla-daemon
2010-09-16 18:05 ` bugzilla-daemon
2010-09-16 18:38 ` 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-29901-502@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.