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 28054] New: Every application accessing GL segfaults
Date: Mon, 10 May 2010 11:34:04 -0700 (PDT)	[thread overview]
Message-ID: <bug-28054-502@http.bugs.freedesktop.org/> (raw)

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

           Summary: Every application accessing GL segfaults
           Product: Mesa
           Version: git
          Platform: x86-64 (AMD64)
        OS/Version: Linux (All)
            Status: NEW
          Severity: major
          Priority: medium
         Component: Drivers/DRI/R600
        AssignedTo: dri-devel@lists.freedesktop.org
        ReportedBy: g.galwas@highantdev.de


Created an attachment (id=35549)
 --> (https://bugs.freedesktop.org/attachment.cgi?id=35549)
output of gdb without debug symbols with backtrace (bt command)

I updated libdrm+ddx+mesa today.

Every application I tried: wine, glxgears, glxinfo, alien-arena segfaults:

Example:

mcgreg@pegasos:~$ glxinfo 
name of display: :0.0
Segmentation fault

dmesg: 
glxinfo[6061]: segfault at 11 ip 00007fbf254efd44 sp 00007fffa24c06f0 error 4
in libpthread-2.10.2.so[7fbf254e7000+16000]

-- 
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-05-10 18:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-10 18:34 bugzilla-daemon [this message]
2010-05-10 18:37 ` [Bug 28054] Every application accessing GL segfaults bugzilla-daemon
2010-05-10 18:55 ` bugzilla-daemon
2010-05-10 19:00 ` bugzilla-daemon
2010-05-10 19:12 ` 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-28054-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