dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 42908] New: r600g: glx-shader-sharing causes segfault
Date: Mon, 14 Nov 2011 11:34:59 +0000	[thread overview]
Message-ID: <bug-42908-502@http.bugs.freedesktop.org/> (raw)

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

             Bug #: 42908
           Summary: r600g: glx-shader-sharing causes segfault
    Classification: Unclassified
           Product: Mesa
           Version: git
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/Gallium/r600
        AssignedTo: dri-devel@lists.freedesktop.org
        ReportedBy: debian@carbon-project.org


Created attachment 53511
  --> https://bugs.freedesktop.org/attachment.cgi?id=53511
GDB ouput for the crash

I'm currently trying to find the Piglit test (it's one of the GLX tests run by
r600.tests), that causes screen corruption. In the process I hit a segfault in
r600_dri.so, which I can cause repeatedly with glx-shader-sharing.

Used stack:
Mesa: Git/9ae10e9c
libdrm: 2.4.27-1
Kernel: 3.1.1
X.org: 1.11.1.902-1

The attachment shows a backtrace and a register dump. Let me know, if you need
more.

-- 
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-11-14 11:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-14 11:34 bugzilla-daemon [this message]
2011-11-14 11:35 ` [Bug 42908] r600g: glx-shader-sharing causes segfault bugzilla-daemon
2011-11-15 16:31 ` 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-42908-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox