-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Ian Romanick wrote:
> Mike Mestnik wrote:
>
>>>How do I prove that? I'm thinking they might try and say that a
>>>software mesa path is calling this, I'd assume that internally you
>>>would call something like _glStencilFunc.
>>>
>>>My other problem is that if the error is caught, why is the screen all
>>>black? What would be the next step in tracking this down be?
>
> Figure out what value is being passed to glStencilFunc. Try applying
> the attached patch. That will print the value of the stencil function
> to the error message that you're already getting.
I don't know why the patch file was empty. Let's try again...
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
iD8DBQFElsj3X1gOwKyEAw8RAjt2AJ9jK6Wj2oHOSePtof0vrSzlHCuvsQCfbbLh
Gl6fQQ86U0QgEvFATlSW/LU=
=K2RZ
-----END PGP SIGNATURE-----
Index: src/mesa/main/stencil.c
===================================================================
RCS file: /cvs/mesa/Mesa/src/mesa/main/stencil.c,v
retrieving revision 1.38
diff -u -d -r1.38 stencil.c
--- src/mesa/main/stencil.c 20 Sep 2005 04:31:24 -0000 1.38
+++ src/mesa/main/stencil.c 19 Jun 2006 15:55:17 -0000
@@ -109,7 +109,7 @@
case GL_ALWAYS:
break;
default:
- _mesa_error( ctx, GL_INVALID_ENUM, "glStencilFunc" );
+ _mesa_error( ctx, GL_INVALID_ENUM, "glStencilFunc (0x%04x)", func );
return;
}
--
_______________________________________________
Dri-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dri-devel
