[Bug 101330] segfault in pcsxr
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Fri Jun 23 18:15:17 UTC 2017
https://bugs.freedesktop.org/show_bug.cgi?id=101330
--- Comment #6 from Vincent B. <vb at luminar.eu.org> ---
Core was generated by `pcsxr'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0xe64f8128 in radeon_bo_do_map (bo=0x931b0f8) at radeon_drm_bo.c:466
466 radeon_drm_bo.c: Aucun fichier ou dossier de ce type.
[Current thread is 1 (Thread 0xf5ab2fc0 (LWP 4362))]
(gdb) bt
#0 0xe64f8128 in radeon_bo_do_map (bo=0x931b0f8) at radeon_drm_bo.c:466
#1 0xe6529342 in r600_buffer_transfer_map (ctx=0x965c168, resource=0x955cc30,
level=0, usage=3758099970, box=0xffad0cc8, ptransfer=0x9313f54) at
r600_buffer_common.c:480
#2 0xe620e6d8 in tc_transfer_map (_pipe=0x9771850, resource=0x955cc30,
level=0, usage=3758099970, box=0xffad0cc8, transfer=0x9313f54) at
util/u_threaded_context.c:1396
#3 0xe5fd1384 in pipe_buffer_map_range (transfer=0x9313f54, access=<optimized
out>, length=65536, offset=0, buffer=<optimized out>, pipe=<optimized out>) at
../../src/gallium/auxiliary/util/u_inlines.h:307
#4 st_bufferobj_map_range (ctx=0x97796c8, offset=0, length=65536,
access=16438, obj=0x9313ed8, index=MAP_INTERNAL) at
state_tracker/st_cb_bufferobjects.c:433
#5 0xe5fad656 in vbo_exec_vtx_map (exec=0x979dadc) at vbo/vbo_exec_draw.c:342
#6 0xe5f98114 in vbo_Vertex3fv (v=0xe6afaec0 <vertex>) at
vbo/vbo_attrib_tmp.h:280
#7 0xe6ab5842 in primTileS () from /home/vb/.pcsxr/plugins//libpeopsxgl.so
#8 0xe6aacf01 in GPUwriteDataMem () from
/home/vb/.pcsxr/plugins//libpeopsxgl.so
#9 0xe6aad44c in GPUdmaChain () from /home/vb/.pcsxr/plugins//libpeopsxgl.so
#10 0x080961f1 in ?? ()
#11 0x08097042 in ?? ()
#12 0xf4d77fbd in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20170623/b64560a0/attachment.html>
More information about the dri-devel
mailing list