All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 39193] [llvmpipe and r600g] glCheckFramebufferStatusEXT segfaults in Gallium when checking status on a framebuffer bound to a texture that's bound to a pixmap
Date: Thu, 22 Sep 2011 08:07:35 -0700 (PDT)	[thread overview]
Message-ID: <20110922150735.61547130140@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-39193-502@http.bugs.freedesktop.org/>

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

--- Comment #6 from Michel Dänzer <michel@daenzer.net> 2011-09-22 08:07:34 PDT ---
Note that a bug shouldn't be resolved before the fix lands in Git, but it has
now.

BTW, I was confused for a while by a latent bug of the test program: It leaves
bound_texture uninitialized, and when it ends up being 0, the texture fails to
attach to the framebuffer, and that ends up incomplete.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

      parent reply	other threads:[~2011-09-22 15:07 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 ` [Bug 39193] " bugzilla-daemon
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 [this message]

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=20110922150735.61547130140@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.