dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 106289] mupen64plus segfaults deep inside r300_dri.so
Date: Sat, 12 May 2018 21:56:07 +0000	[thread overview]
Message-ID: <bug-106289-502-CbW0QdeIrm@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-106289-502@http.bugs.freedesktop.org/>


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

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

--- Comment #1 from Dave Coffin <dcoffin@cybercom.net> ---
This bug also crashes "mplayer" but not "mpv".  I compiled mesa 18.0.3 from
source and got a more informative stack trace, though many parameters are still
"optimized out":

r300: DRM version: 2.50.0, Name: ATI RS480, ID: 0x5975, GB: 2, Z: 1
r300: GART size: 509 MB, VRAM size: 128 MB
r300: AA compression RAM: YES, Z compression RAM: YES, HiZ RAM: NO
r300: DRM version: 2.50.0, Name: ATI RS480, ID: 0x5975, GB: 2, Z: 1
r300: GART size: 509 MB, VRAM size: 128 MB
r300: AA compression RAM: YES, Z compression RAM: YES, HiZ RAM: NO
Core: Setting 32-bit video mode: 640x480
r300: DRM version: 2.50.0, Name: ATI RS480, ID: 0x5975, GB: 2, Z: 1
r300: GART size: 509 MB, VRAM size: 128 MB
r300: AA compression RAM: YES, Z compression RAM: YES, HiZ RAM: NO
r300: DRM version: 2.50.0, Name: ATI RS480, ID: 0x5975, GB: 2, Z: 1
r300: GART size: 509 MB, VRAM size: 128 MB
r300: AA compression RAM: YES, Z compression RAM: YES, HiZ RAM: NO
Video Warning: Failed to set GL_SWAP_CONTROL to 0. (it's 24)
Video Warning: Failed to set GL_BUFFER_SIZE to 32. (it's 24)
Video Warning: Failed to set GL_DEPTH_SIZE to 16. (it's 24)
Video: Using OpenGL: X.Org R300 Project - ATI RS480 : 2.1 Mesa 18.0.3

Thread 1 "mupen64plus" received signal SIGSEGV, Segmentation fault.
0xb4c12200 in ?? ()
(gdb) where
#0  0xb4c12200 in ?? ()
#1  0xb35b5bfb in llvm_pipeline_generic (middle=0x6964c0,
middle@entry=0x64aa80, 
    fetch_info=fetch_info@entry=0xbffb688c,
in_prim_info=in_prim_info@entry=0xbffb689c)
    at draw/draw_pt_fetch_shade_pipeline_llvm.c:400
#2  0xb35b62af in llvm_middle_end_linear_run (middle=0x64aa80, start=0,
count=<optimized out>, 
    prim_flags=0) at draw/draw_pt_fetch_shade_pipeline_llvm.c:553
#3  0xb34b04db in vsplit_segment_simple_linear (vsplit=0x648420,
vsplit=0x648420, icount=4, istart=0, 
    flags=0) at draw/draw_pt_vsplit_tmp.h:226
#4  vsplit_run_linear (frontend=0x648420, start=0, count=4) at
draw/draw_split_tmp.h:60
#5  0xb34a8140 in draw_pt_arrays (draw=draw@entry=0x552810, prim=6, start=0,
count=4)
    at draw/draw_pt.c:149
#6  0xb34a8677 in draw_vbo (draw=<optimized out>, info=<optimized out>) at
draw/draw_pt.c:564
#7  0xb35e41bb in r300_swtcl_draw_vbo (pipe=0x5124f0, info=0xbffb6a70) at
r300_render.c:862
#8  0xb34f3fd6 in util_draw_arrays_instanced (mode=PIPE_PRIM_TRIANGLE_FAN,
start=0, count=4, 
    start_instance=0, instance_count=1, pipe=0x5124f0) at ./util/u_draw.h:106
#9  blitter_draw (ctx=<optimized out>, vertex_elements_cso=<optimized out>, 
    get_vs=0xb34f3790 <get_vs_passthrough_pos>, x1=0, y1=0, x2=640, y2=480,
depth=1, num_instances=1)
    at util/u_blitter.c:1257
#10 0xb34f4176 in util_blitter_draw_rectangle (blitter=<optimized out>, 
    vertex_elements_cso=<optimized out>, get_vs=<optimized out>, x1=<optimized
out>, 
    y1=<optimized out>, x2=<optimized out>, y2=480, depth=1, num_instances=1, 
    type=UTIL_BLITTER_ATTRIB_NONE, attrib=0xbffb6ba4) at util/u_blitter.c:1291
#11 0xb35e63f5 in r300_blitter_draw_rectangle (blitter=0x528760,
vertex_elements_cso=0x682830, 
    get_vs=0xb34f3790 <get_vs_passthrough_pos>, x1=0, y1=0, x2=640, y2=480,
depth=1, num_instances=1, 
    type=UTIL_BLITTER_ATTRIB_NONE, attrib=0xbffb6ba4) at r300_render.c:1139
#12 0xb34f6dc7 in util_blitter_clear_custom (blitter=0x528760, width=640,
height=480, num_layers=1, 
    clear_buffers=1, color=0x628634, depth=1, stencil=0, custom_dsa=0x0,
custom_blend=0x0)
    at util/u_blitter.c:1411
#13 0xb34f6f33 in util_blitter_clear (blitter=<optimized out>, width=<optimized
out>, 
    height=<optimized out>, num_layers=<optimized out>,
clear_buffers=<optimized out>, 
    color=<optimized out>, depth=<optimized out>, stencil=0) at
util/u_blitter.c:1428
#14 0xb35d828e in r300_clear (pipe=0x5124f0, buffers=1, color=0x628634,
depth=1, stencil=0)
    at r300_blit.c:368
#15 0xb329d564 in st_Clear (ctx=<optimized out>, mask=<optimized out>)
    at state_tracker/st_cb_clear.c:483
#16 0xb30d455c in clear (no_error=false, mask=<optimized out>, ctx=0x627140) at
main/clear.c:221
#17 _mesa_Clear (mask=<optimized out>) at main/clear.c:242
#18 0xb4ca782d in ?? () from
/usr/lib/i386-linux-gnu/mupen64plus/mupen64plus-video-rice.so
#19 0xb4c93574 in ?? () from
/usr/lib/i386-linux-gnu/mupen64plus/mupen64plus-video-rice.so
#20 0xb4c81475 in RomOpen () from
/usr/lib/i386-linux-gnu/mupen64plus/mupen64plus-video-rice.so
#21 0xb6406c0c in ?? () from /usr/lib/i386-linux-gnu/libmupen64plus.so.2
#22 0xb6407618 in CoreDoCommand () from
/usr/lib/i386-linux-gnu/libmupen64plus.so.2
#23 0x00402d50 in main ()

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

[-- Attachment #1.2: Type: text/html, Size: 5779 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

  parent reply	other threads:[~2018-05-12 21:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-28  2:30 [Bug 106289] mupen64plus segfaults deep inside r300_dri.so bugzilla-daemon
2018-04-30  9:34 ` bugzilla-daemon
2018-05-12 21:56 ` bugzilla-daemon [this message]
2018-05-13 17:27 ` bugzilla-daemon
2018-06-06  4:44 ` bugzilla-daemon
2018-06-08  0:12 ` bugzilla-daemon
2019-09-18 18:54 ` 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-106289-502-CbW0QdeIrm@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