Part of the Khronos Group
OpenGL.org

The Industry's Foundation for High Performance Graphics

from games to virtual reality, mobile phones to supercomputers

Results 1 to 7 of 7

Thread: glPushDebugGroup() broken in AMD 13.12 WHQL drivers ?

  1. #1
    Junior Member Newbie
    Join Date
    May 2002
    Posts
    25

    Question glPushDebugGroup() broken in AMD 13.12 WHQL drivers ?

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

    It has this example:
    Code :
        // 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");

    This results in a GL_INVALID_OPERATION when glPushDebugGroup() is called.

    I do not see any new versions of openGL I can try, since 14.1 & 14.2 BETA drivers do not support Vista 64bit it seems.

    Funny enough, 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.
    This is on a 6870 card, using 13.12 WHQL drivers.

  2. #2
    Senior Member OpenGL Pro
    Join Date
    Jan 2012
    Location
    Australia
    Posts
    1,117
    I will try to test this on a AMD machine but the code worked fine on nVidia driver 331.82

  3. #3
    Member Regular Contributor malexander's Avatar
    Join Date
    Aug 2009
    Location
    Ontario
    Posts
    315
    I ran into an AMD driver bug where -1 for the string length was being rejected as an invalid value, instead of indicating a NULL-terminated string. Passing strlen(msg) worked around the issue. Not sure if this is the same bug.

  4. #4
    Junior Member Newbie
    Join Date
    May 2002
    Posts
    25
    OpenGL Vendor: ATI Technologies Inc.
    OpenGL Renderer: AMD Radeon HD 6800 Series
    OpenGL Version: 4.3.12798 Compatibility Profile Context 13.251.0.0
    Still broken in the just released 14.3 v1 beta drivers.

    malexander, no, that isn't the issue here.

  5. #5
    Junior Member Newbie
    Join Date
    May 2002
    Posts
    25
    Quote Originally Posted by glDan View Post
    Still broken in the just released 14.3 v1 beta drivers.
    Make that, the windows drivers of 14.3 v1 beta is broken. The linux 14.3 v1 beta work as expected.

  6. #6
    Junior Member Newbie
    Join Date
    May 2002
    Posts
    25
    Quote Originally Posted by glDan View Post
    Make that, the windows drivers of 14.3 v1 beta is broken. The linux 14.3 v1 beta work as expected.
    OpenGL Version: 4.4.12874 Compatibility Profile Context 14.100.0.0 is still broken.
    Those are 14.4 WHQL ones, released yesterday.

  7. #7
    Junior Member Newbie
    Join Date
    May 2002
    Posts
    25
    Quote Originally Posted by glDan View Post
    OpenGL Version: 4.4.12874 Compatibility Profile Context 14.100.0.0 is still broken. Those are 14.4 WHQL ones, released yesterday.
    Finally fixed in the 14.6's BETA drivers. OpenGL Version: 4.4.12967 Compatibility Profile Context 14.100.0.0

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •