Expose GL_ANGLE_framebuffer_blit in NULL backend

The passthrough ASAN fuzzer was hitting a null-dereference trying to call glBlitFramebuffer when ANGLE was not exposing it. The fuzzer uses the NULL backend so we can just expose it. Bug: chromium:1029829 Change-Id: I0f65c65284756fa21821155559a6404d95e25647 Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2003230Reviewed-by: Geoff Lang <geofflang@chromium.org> Commit-Queue: Jonah Ryan-Davis <jonahr@google.com>

Expose GL_ANGLE_framebuffer_blit in NULL backend
df0683b1 · Jonah Ryan-Davis · Commit Bot · 01c0d6bd · df0683b1
Commit df0683b1 authored Jan 15, 2020 by Jonah Ryan-Davis Committed by Commit Bot Jan 16, 2020
Hide whitespace changes
Inline Side-by-side

Showing with 1 addition and 0 deletions

ContextNULL.cpp src/libANGLE/renderer/null/ContextNULL.cpp +1 -0

No files found.
--- a/src/libANGLE/renderer/null/ContextNULL.cpp
+++ b/src/libANGLE/renderer/null/ContextNULL.cpp
@@ -69,6 +69,7 @@ ContextNULL::ContextNULL(const gl::State &state,
    mExtensions                        = gl::Extensions();
    mExtensions.fence                  = true;
+    mExtensions.framebufferBlit        = true;
    mExtensions.instancedArraysANGLE   = true;
    mExtensions.instancedArraysEXT     = true;
    mExtensions.pixelBufferObject      = true;