4 Replies Latest reply on Apr 26, 2014 6:55 PM by Quartz

    glPushDebugGroup() broken in 13.12 WHQL drivers

    Quartz

      6.14.10.12618 (13.12 WHQL) drivers, doing glPushDebugGroup() causes GL_INVALID_OPERATION.

      Using a 6870 card for testing.

       

      From: http://www.opengl.org/registry/specs/KHR/debug.txt

       

      Trying:

      // Setup of the default active debug group: Filter everything in
        glDebugMessageControl(GL_DONT_CARE, GL_DONT_CARE, GL_DONT_CARE, 0, NULL, GL_TRUE);
      
        // Generate a debug marker debug output message
        glDebugMessageInsert(
        GL_DEBUG_SOURCE_APPLICATION,
        GL_DEBUG_TYPE_MARKER, 100,
        GL_DEBUG_SEVERITY_NOTIFICATION,
        -1, "Message 1");
      
        // Push debug group 1
        glPushDebugGroup(
        GL_DEBUG_SOURCE_APPLICATION,
        1,
        -1, "Message 2");
      
      
      
      
      

      returns GL_INVALID_OPERATION at the glPushDebugGroup() call.

       

      There are no other openGL drivers to try that are newer than 6.14.10.12618 for vista 64bit.  AMD don't seem to offer BETA drivers for 14.1 or 14.2 for Vista 64bit.

       

      looking at http://www.opengl.org/sdk/docs/man/d...DebugGroup.xml

      for errors, it lists:

       

      Errors

      GL_INVALID_ENUM is generated if the value of source is neither GL_DEBUG_SOURCE_APPLICATION nor GL_DEBUG_SOURCE_THIRD_PARTY.
      GL_INVALID_VALUE is generated if length is negative and the number of characters in message, excluding the null-terminator, is not less than the value of GL_MAX_DEBUG_MESSAGE_LENGTH.

      So, GL_INVALID_OPERATION isn't even listed as a possible error, so, this looks like a driver bug.

       

      Yeah, I am sure it is the glPushDebugGroup() call that causes that error, I added glGetError() calls between and before all calls.