On Fri, Feb 19, 2010 at 7:34 PM, Xavier Chantry <chantry.xav...@gmail.com> wrote: > It seems the commit below will always report an user error when > glxinfo -l is called. > And indeed I always get the following : > $ glxinfo -l > ... > GL_VERTEX_PROGRAM_ARB: > ... > Mesa: User error: GL_INVALID_ENUM in glGetProgramivARB(pname) > Mesa: User error: GL_INVALID_ENUM in glGetProgramivARB(pname) > Mesa: User error: GL_INVALID_ENUM in glGetProgramivARB(pname) > Mesa: User error: GL_INVALID_ENUM in glGetProgramivARB(pname) > Mesa: User error: GL_INVALID_ENUM in glGetProgramivARB(pname) > Mesa: User error: GL_INVALID_ENUM in glGetProgramivARB(pname) > > Should glxinfo be fixed to avoid this error ? > We could just put the fragment program only parameter in its own list, > and not use them when target is vertex program.
Well, normally GL errors aren't reported to stderr so most people running non-debug builds won't see those. But yeah, we probably shouldn't generate the errors anyway. Feel free to write a patch to glxinfo... -Brian ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Mesa3d-dev mailing list Mesa3d-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
