From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 106289] mupen64plus segfaults deep inside r300_dri.so
Date: Sat, 28 Apr 2018 02:30:27 +0000 [thread overview]
Message-ID: <bug-106289-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2542 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=106289
Bug ID: 106289
Summary: mupen64plus segfaults deep inside r300_dri.so
Product: DRI
Version: XOrg git
Hardware: x86 (IA32)
OS: Linux (All)
Status: NEW
Severity: blocker
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: dcoffin@cybercom.net
Dell Vostro 1000 laptop with Mobile AMD Sempron, Mobility Radeon Xpress 200,
and 32-bit Linux (though CPU is capable of 64-bit). "apt install mupen64plus",
run it with any game ROM -- it opens an all-black window, pauses for a few
seconds, and segfaults in r300_dri.so. mupen64plus worked great in Kubuntu
17.04 but always crashes in 17.10 and 18.04.
Video: SSE processing enabled.
Video: Found ROM 'SUPER MARIO 64', CRC ff2b5a632623028b-45
Video: Initializing OpenGL Device Context.
warning: Error reading shared library list entry at 0x5f20
warning: Error reading shared library list entry at 0xffffbf40
Core: Setting 32-bit video mode: 640x480
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.0-rc5
Thread 1 "mupen64plus" received signal SIGSEGV, Segmentation fault.
0xb4a83200 in ?? ()
(gdb) where
#0 0xb4a83200 in ?? ()
#1 0xb33fff48 in ?? () from /usr/lib/i386-linux-gnu/dri/r300_dri.so
#2 0xb34004df in ?? () from /usr/lib/i386-linux-gnu/dri/r300_dri.so
#3 0xb33132f9 in ?? () from /usr/lib/i386-linux-gnu/dri/r300_dri.so
#4 0xb330c1c0 in ?? () from /usr/lib/i386-linux-gnu/dri/r300_dri.so
#5 0xb330c6b7 in ?? () from /usr/lib/i386-linux-gnu/dri/r300_dri.so
#6 0xb353e21b in ?? () from /usr/lib/i386-linux-gnu/dri/r300_dri.so
#7 0xb33511e4 in ?? () from /usr/lib/i386-linux-gnu/dri/r300_dri.so
#8 0xb353fcd5 in ?? () from /usr/lib/i386-linux-gnu/dri/r300_dri.so
#9 0xb33539ee in ?? () from /usr/lib/i386-linux-gnu/dri/r300_dri.so
#10 0xb35342b6 in ?? () from /usr/lib/i386-linux-gnu/dri/r300_dri.so
#11 0xb3127955 in ?? () from /usr/lib/i386-linux-gnu/dri/r300_dri.so
#12 0xb2f7892f in ?? () from /usr/lib/i386-linux-gnu/dri/r300_dri.so
#13 0xb4caa82d in ?? () from
/usr/lib/i386-linux-gnu/mupen64plus/mupen64plus-video-rice.so
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3855 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 reply other threads:[~2018-04-28 2:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-28 2:30 bugzilla-daemon [this message]
2018-04-30 9:34 ` [Bug 106289] mupen64plus segfaults deep inside r300_dri.so bugzilla-daemon
2018-05-12 21:56 ` bugzilla-daemon
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@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.