[Mesa-dev] [Bug 65173] segfault in _mesa_get_format_datatype and _mesa_get_color_read_type when state dumping with glretrace

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Thu May 30 23:35:43 PDT 2013


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

--- Comment #11 from José Fonseca <jfonseca at vmware.com> ---
(In reply to comment #10)
> >What does nVidia proprietary driver return for 
> >IMPLEMENTATION_COLOR_READ_{FORMAT,TYPE} on that call? That is, what is the 
> >output of
> > glretrace -D 137078 wine-preloader.137078.trim.trace | grep 
> >IMPLEMENTATION_COLOR_READ
> 
> Nothing, the part of the state dump where mesa version crashes looks like
> this (I've put stderr part in <stderr> tags):
> 
>  "GL_MAX_VERTEX_UNIFORM_COMPONENTS": 4096,
>     "GL_MAX_VARYING_COMPONENTS": 60,
>     "GL_MAX_VERTEX_TEXTURE_IMAGE_UNITS": 32,
>     "GL_MAX_COMBINED_TEXTURE_IMAGE_UNITS": 96,
>     "GL_SHADING_LANGUAGE_VERSION": "3.30 NVIDIA via Cg compiler",
>     "GL_CURRENT_PROGRAM": 18 <stderr>137078: glDebugOutputCallback: High
> severity API error 1282, GL_INVALID_OPERATION error generated. Invalid query
> on incomplete or unselected read framebuffer
> 137078: glDebugOutputCallback: High severity API error 1282,
> GL_INVALID_OPERATION error generated. Invalid query on incomplete or
> unselected read framebuffer</stderr>
> ,
>     "GL_MAX_GEOMETRY_TEXTURE_IMAGE_UNITS": 32,
>     "GL_TEXTURE_BUFFER": 0,

Thanks for checking. It seems it nvidia driver emits a GL_INVALID_OPERATION
error.  We could do the same.

BTW, I did read the relevant specs for this query, but they don't really
describe what happens in this situation.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/mesa-dev/attachments/20130531/d9f22a8c/attachment.html>


More information about the mesa-dev mailing list