All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 36318] New: r600g segfaults
Date: Sat, 16 Apr 2011 22:52:38 -0700 (PDT)	[thread overview]
Message-ID: <bug-36318-502@http.bugs.freedesktop.org/> (raw)

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

           Summary: r600g segfaults
           Product: Mesa
           Version: git
          Platform: x86-64 (AMD64)
        OS/Version: Linux (All)
            Status: NEW
          Severity: major
          Priority: medium
         Component: Drivers/Gallium/r600
        AssignedTo: dri-devel@lists.freedesktop.org
        ReportedBy: ianmllgn@gmail.com


r600g segfaults running glxgears. Here is a backtrace

#0  0x00007ffff5327f6e in loopback_VertexAttrib3svNV (index=1283, v=0x1e08) at
main/api_loopback.c:1137
#1  0x00007ffff532800f in loopback_VertexAttribs3svNV (index=<value optimized
out>, n=<value optimized out>, v=0x2dd) at main/api_loopback.c:1220
#2  0x00007ffff525eed6 in execute_list (ctx=0xb55960, list=<value optimized
out>) at main/dlist.c:8163
#3  0x00007ffff526130a in _mesa_CallList (list=1) at main/dlist.c:8511
#4  0x0000000000401ce2 in draw ()
#5  0x00000000004035c9 in main ()

-- 
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-04-17  5:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-17  5:52 bugzilla-daemon [this message]
2011-04-17  6:37 ` [Bug 36318] r600g segfaults bugzilla-daemon
2011-04-17  9:28 ` bugzilla-daemon
2011-04-17 16:22 ` bugzilla-daemon
2011-04-18 14:33 ` bugzilla-daemon
2011-04-20 15:43 ` 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-36318-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.