wined3d: Print an ERR instead of crashing in context_check_fbo_status().

Some version of Mesa will claim the window system provided framebuffer is incomplete when using indirect rendering, although the framebuffer objects spec says this can never happen. Printing an ERR instead of crashing should make it clearer that this isn't a wined3d problem.

wined3d: Print an ERR instead of crashing in context_check_fbo_status().
483d5d0a · Henri Verbeet · Alexandre Julliard · d03a105c · 483d5d0a
Commit 483d5d0a authored Oct 26, 2009 by Henri Verbeet Committed by Alexandre Julliard Oct 26, 2009
Hide whitespace changes
Inline Side-by-side

Showing with 6 additions and 0 deletions

context.c dlls/wined3d/context.c +6 -0

No files found.
--- a/dlls/wined3d/context.c
+++ b/dlls/wined3d/context.c
@@ -288,6 +288,12 @@ static void context_check_fbo_status(struct wined3d_context *context)
        unsigned int i;
        FIXME("FBO status %s (%#x)\n", debug_fbostatus(status), status);

+        if (!context->current_fbo)
+        {
+            ERR("FBO 0 is incomplete, driver bug?\n");
+            return;
+        }
+
        /* Dump the FBO attachments */
        for (i = 0; i < gl_info->max_buffers; ++i)
        {