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 10 of 12

Thread: GL_ARB_Debug_Output - what do you need ?

Threaded View

  1. #11
    Senior Member OpenGL Pro
    Join Date
    Apr 2010
    Location
    Germany
    Posts
    1,129
    please implement KHR_debug
    For Windows and Linux please. I checked out KHR_debug on Windows with an NVIDIA GPU (due to Ubuntu lacking the GL 4.3 beta blob on Linux as of yet) a few days ago and the messages are quite informative regarding stuff like invalid enums and such. However, you get bombarded with the error each frame if you just use the callback. If there are any ways to keep the info around while being able to manage the flood of messages please tell.

    I want to add another item to the wish list: redundant state changes. gDEBugger tracks it, so could the driver and spit out the command, possibly some info on the arguments and the current state to get a clue of where the call was possibly made.

    Also, I noticed that KHR_debug on NVIDIA informs of a

    Quote Originally Posted by Le Spec
    GL_INVALID_OPERATION is generated if program could not be made part of current state.
    if you call glUseProgram() and some stages could not be compiled or linked - as the quote says. I noticed that when a geometry shader was accidentally attached but didn't have any source and thus could not be compiled.

    So, to summarize my personal wishlist:

    • info on pipeline stalls, maybe as a ratio or even more informative if possibly (performance)
    • info on redundant state changes (performance)
    • info on shader program correctness (debug)
    Last edited by thokra; 09-21-2012 at 12:36 AM.

Posting Permissions

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