Closed mklingen closed 6 years ago
I wouldn’t be opposed to making the Exception print the message too - just add it to both OpenGLDevice_GL and ModernGLDevice_GL and I can merge it in.
Cool, will make a PR when I get the chance.
Actually thinking about it, you can probably just replace my ARB string with just the error message - by the time you hit a fatal error the message on its own should be pretty clear (minus the fact that errors are usually generated by programs like XSplit or other programs I wish I could outwardly call malware)...
Our application has automatic crash reporting based on exception handling. Occasionally, we get exceptions reported like this one: https://github.com/CompletelyFairGames/dwarfcorp/issues/706
Such exceptions are difficult to debug because the actual content of the warning or error seems to just get
printfed
to the console (or in our case, a local log file). Is there a way to get the actual content of the warning when the exception is created? Or is there a way to capture such warnings when they occur so we can report them?