Re: wined3d: Initialize maxAttribs in case it isn't changed by glGetIntegerv.

[Stefan Dösinger]

Am Samstag, 22. März 2008 18:28:52 schrieb Philip Nilsson:
> My OpenGL implementation (NVIDIA's binary driver, version 169.12)
> returns GL_NO_ERROR in this function, but doesn't change the passed
> value.  Uninitialized maxAttribs might be about 1500000 and thus
> generate a couple hundred megabytes of GL_CHECK_CALL errors.
>
> 16 is what is set if glGetIntegerv returns some error, and is also the
> minimum value required by an implementation.

I've seen this behavior very old drivers(87.xx), but I am kinda puzzled why it 
happens with the new drivers. The patch is OK, but we should investigate why 
the call fails for you

wined3d: Initialize maxAttribs in case it isn't changed by glGetIntegerv.

[Philip Nilsson]

On Sat, Mar 22, 2008 at 08:04:52PM +0100, Stefan Dösinger wrote:
> Am Samstag, 22. März 2008 18:28:52 schrieb Philip Nilsson:
> > glGetIntegerv
>
> I've seen this behavior very old drivers(87.xx), but I am kinda puzzled why it 
> happens with the new drivers. The patch is OK, but we should investigate why 
> the call fails for you

It appears to do nothing whichever enum I query.  It doesn't even care
if it's fed (-1, NULL).

I'll try some things.