From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 37474] New: Segmentation Fault in glCopyTexSubImage2D
Date: Sun, 22 May 2011 11:41:52 -0700 (PDT) [thread overview]
Message-ID: <bug-37474-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=37474
Summary: Segmentation Fault in glCopyTexSubImage2D
Product: Mesa
Version: 7.10
Platform: PowerPC
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/DRI/r128
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: asguthrie@gmail.com
Created an attachment (id=47011)
--> (https://bugs.freedesktop.org/attachment.cgi?id=47011)
stracktrace
projectM-pulseaudio seg faults whilst calling glCopyTextSubImage2D.
stacktrace attached.
patch inspired by bug #27652 also attached.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2011-05-22 18:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-22 18:41 bugzilla-daemon [this message]
2011-05-22 18:43 ` [Bug 37474] Segmentation Fault in glCopyTexSubImage2D bugzilla-daemon
2018-01-30 1:17 ` bugzilla-daemon
2018-01-30 16:10 ` 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-37474-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;
as well as URLs for NNTP newsgroup(s).