Enable all debug output in glretrace #223
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
On nVidia systems, not all debug output is enabled by default. If we wish to have the driver tell us where it is placing buffer objects, for example, we have to enable all the debug channels by passing GL_DONT_CARE to everything in glDebugMessageControlARB(...)
|
Pushed. Thanks. I had to add a limit to low severity messages, as some traces would become just too noisy ( fe6bb2b ). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
On (at least) nVidia systems, not all debug output is enabled by default. If we wish to have the driver tell us where it is placing buffer objects, for example, we have to enable all the debug channels by passing GL_DONT_CARE to everything in glDebugMessageControlARB(...).
The extra messages I get with this enabled, while not technically errors, can be useful diagnosing some types of performance issue. For example:
"Low severity API unknown issue 131185, Buffer detailed info: Buffer object 1 (bound to GL_PIXEL_UNPACK_BUFFER_ARB, usage hint is GL_DYNAMIC_DRAW) has been mapped in DMA CACHED memory."
Thoughts?
— David