All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 32456] New: r600g makes sdlmame SIGSEGV, r600_set_vertex_buffers involvement indicated
Date: Thu, 16 Dec 2010 14:38:53 -0800 (PST)	[thread overview]
Message-ID: <bug-32456-502@http.bugs.freedesktop.org/> (raw)

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

           Summary: r600g makes sdlmame SIGSEGV, r600_set_vertex_buffers
                    involvement indicated
           Product: Mesa
           Version: git
          Platform: x86-64 (AMD64)
        OS/Version: Linux (All)
            Status: NEW
          Severity: normal
          Priority: low
         Component: Drivers/Gallium/r600
        AssignedTo: dri-devel@lists.freedesktop.org
        ReportedBy: oyvinds@everdot.org


1. run sdlmame.
2. it dies on SIGSEGV, Segmentation fault.

gdb sdlmame
(gdb) run -video opengl -rompath /public/net/godzilla/games/MAME/roms/ mslug2
Starting program: /usr/games/bin/sdlmame -video opengl -rompath
/public/net/godzilla/games/MAME/roms/ mslug2
[Thread debugging using libthread_db enabled]
Warning: unknown option in INI: useallheads
Warning: unknown option in INI: useallheads
[New Thread 0x7ffff427e710 (LWP 29182)]
[New Thread 0x7ffff04e9710 (LWP 29183)]
WARNING: Couldn't find/open TrueType font Liberation Sans, using MAME default

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff2188339 in r600_set_vertex_buffers () from
/usr/lib64/dri/r600_dri.so
(gdb) bt
#0  0x00007ffff2188339 in r600_set_vertex_buffers () from
/usr/lib64/dri/r600_dri.so
#1  0x00007ffff223959c in st_draw_vbo () from /usr/lib64/dri/r600_dri.so
#2  0x00007ffff22362a3 in vbo_draw_arrays () from /usr/lib64/dri/r600_dri.so
#3  0x0000000000ff96f9 in drawogl_window_draw(_sdl_window_info*, unsigned int,
int) ()
#4  0x0000000000ff1cc6 in draw_video_contents_wt(void*, int) ()
#5  0x0000000000ff2fc6 in sdlwindow_video_window_update(running_machine*,
_sdl_window_info*) ()
#6  0x0000000000fd39ac in sdl_osd_interface::update(bool) ()
#7  0x00000000016206c4 in video_manager::frame_update(bool) ()
#8  0x00000000015ebd47 in display_loading_rom_message(_romload_private*, char
const*) ()
#9  0x00000000015ecf9f in process_rom_entries(_romload_private*, char const*,
rom_entry const*) ()
#10 0x00000000015edf17 in rom_init(running_machine*) ()
#11 0x0000000001597b02 in running_machine::start() ()
#12 0x000000000159803b in running_machine::run(bool) ()
#13 0x00000000015963d0 in mame_execute(osd_interface&, _core_options*) ()
#14 0x000000000154fbe5 in cli_execute(int, char**, osd_interface&,
_options_entry const*) ()
#15 0x0000000000fd03bf in main ()
(gdb) quit

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

             reply	other threads:[~2010-12-16 22:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-16 22:38 bugzilla-daemon [this message]
2010-12-17 19:36 ` [Bug 32456] r600g makes sdlmame SIGSEGV, r600_set_vertex_buffers involvement indicated bugzilla-daemon
2010-12-17 21:34 ` bugzilla-daemon
2010-12-17 22:27 ` bugzilla-daemon
2010-12-17 22:56 ` bugzilla-daemon
2010-12-17 23:03 ` 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-32456-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.