All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 41579] New: R300 Segfaults when using mupen64plus
Date: Fri,  7 Oct 2011 17:52:17 -0700 (PDT)	[thread overview]
Message-ID: <bug-41579-502@http.bugs.freedesktop.org/> (raw)

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

           Summary: R300 Segfaults when using mupen64plus
           Product: Mesa
           Version: 7.11
          Platform: x86 (IA32)
        OS/Version: Linux (All)
            Status: NEW
          Severity: major
          Priority: medium
         Component: Drivers/DRI/r300
        AssignedTo: dri-devel@lists.freedesktop.org
        ReportedBy: krthurow@gmail.com


Created an attachment (id=52103)
 --> (https://bugs.freedesktop.org/attachment.cgi?id=52103)
Backtrace from r300 segfault when running mupen64plus.

When starting up the emulator mupen64plus with a ROM, it crashes before loading
the ROM, showing a segfault. Video card is a Mobility Radeon X1700.

Using gdb I traced the segfault back to r300_dri.so
The issues seems to be at line 864 of src/gallium/drivers/r300/r300_emit.c
'buf' is getting set to 0 instead of a proper address.

My backtrace is attached.

-- 
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:[~2011-10-08  0:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-08  0:52 bugzilla-daemon [this message]
2011-10-10 11:22 ` [Bug 41579] R300 Segfaults when using mupen64plus bugzilla-daemon
2011-10-10 11:30 ` bugzilla-daemon
2011-10-11 19:19 ` bugzilla-daemon
2011-10-12  9:59 ` bugzilla-daemon
2011-11-07 20:03 ` bugzilla-daemon
2012-12-05 16:14 ` 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-41579-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.