From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 39193] glCheckFramebufferStatusEXT segfaults in Gallium when checking status on a framebuffer bound to a texture that's bound to a pixmap
Date: Thu, 14 Jul 2011 09:54:34 -0700 (PDT) [thread overview]
Message-ID: <20110714165434.6856A1300FD@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-39193-502@http.bugs.freedesktop.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=39193
--- Comment #1 from Simon Farnsworth <simon.farnsworth@onelan.co.uk> 2011-07-14 09:54:34 PDT ---
I'm going to hunt for a different way to do this; I can see what's going on,
but I have no idea why.
glXBindTexImageEXT ends up calling into st_context_teximage (st_manager.c:523
onwards in my git checkout). When st_context_teximage is about to exit
(returning TRUE), I can see that stObj and stImage have been successfully
initialised, but that stImage->pt is NULL.
When I call glFramebufferTexture2DEXT, the same stObj as st_context_teximage
set up is used; this step works, because it never looks at the pt member.
When I call glCheckFramebufferStatusEXT, I get burnt - st_validate_attachment
deferences pt without checking it for NULL, and thus I segfault out.
I can't work out how stImage->pt is meant to be set; it looks like it might be
a side-effect of pipe_resource_reference, but it isn't happening.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2011-07-14 16:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-13 14:41 [Bug 39193] New: glCheckFramebufferStatusEXT segfaults in Gallium when checking status on a framebuffer bound to a texture that's bound to a pixmap bugzilla-daemon
2011-07-14 16:54 ` bugzilla-daemon [this message]
2011-09-12 21:24 ` [Bug 39193] [r600g] " bugzilla-daemon
2011-09-12 22:16 ` [Bug 39193] [llvmpipe and r600g] " bugzilla-daemon
2011-09-14 12:06 ` bugzilla-daemon
2011-09-14 15:34 ` bugzilla-daemon
2011-09-14 16:31 ` bugzilla-daemon
2011-09-22 15:07 ` 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=20110714165434.6856A1300FD@annarchy.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.