[Mesa-dev] [RFC PATCH shader-db 2/2] run: request a debug context

[Matt Turner]

On Sun, Nov 8, 2015 at 8:53 PM, Ilia Mirkin <imirkin at alum.mit.edu> wrote:
> st/mesa only prints messages in a debug context. Without always enabling
> the message generation, I don't see a way to hook into the glEnable() to
> turn it on/off.
> ---
>  run.c | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/run.c b/run.c
> index 73e468d..1d8d3b1 100644
> --- a/run.c
> +++ b/run.c
> @@ -417,6 +417,7 @@ main(int argc, char **argv)
>          EGL_CONTEXT_OPENGL_CORE_PROFILE_BIT_KHR,
>          EGL_CONTEXT_MAJOR_VERSION_KHR, 3,
>          EGL_CONTEXT_MINOR_VERSION_KHR, 2,
> +        EGL_CONTEXT_FLAGS_KHR, EGL_CONTEXT_OPENGL_DEBUG_BIT_KHR,
>          EGL_NONE
>      };
>      EGLContext core_ctx = eglCreateContext(egl_dpy, cfg, EGL_NO_CONTEXT,

Is this a limitation of st/mesa, or am I using the KHR_debug API
incorrectly? It's my understanding that you can get KHR_debug messages
without a debug context by calling glEnable(GL_DEBUG_OUTPUT), and it
looks like this is supported by the KHR_debug spec.