From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 27566] New: r300g segfaults in glDrawPixels
Date: Fri, 9 Apr 2010 08:36:12 -0700 (PDT) [thread overview]
Message-ID: <bug-27566-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=27566
Summary: r300g segfaults in glDrawPixels
Product: Mesa
Version: git
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/DRI/r300
AssignedTo: dri-devel@lists.sourceforge.net
ReportedBy: wixorpeek@gmail.com
Created an attachment (id=34847)
--> (https://bugs.freedesktop.org/attachment.cgi?id=34847)
the test program (compile with -std=c99)
The attached program causes segfault in r300g. Plain r300 works fine, however
the texture is drawn darkened
Environment:
- Debian Linux, vanilla kernel 2.6.33,
- mesa from git, up to commit 54526154c5b02be0fbae6b0dad766c6be1bee21c
- radeon ddx 1:6.12.192-2 (changelog says: pull from upstream master up to
commit 5c256808)
- libdrm 2.4.18-3
- Radeon x1300 (RV515)
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
--
next reply other threads:[~2010-04-09 15:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-09 15:36 bugzilla-daemon [this message]
2010-04-09 15:37 ` [Bug 27566] r300g segfaults in glDrawPixels bugzilla-daemon
2010-04-09 15:37 ` bugzilla-daemon
2010-04-09 15:47 ` bugzilla-daemon
2010-04-09 16:05 ` 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-27566-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.sourceforge.net \
/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