I compiled G-Truc's 220.127.116.11 samples, but the handling of ARB_debug_output is wrong. Somehow GLEW doesn't utilize a debug context and glGetStringi is an insufficient safeguard. It'll say an extension is present, without enforcing the caveat "but only in a debug context." So the app believes GLEW set up glDebugMessageControlARB, but it segfaults. I'm using an NVIDIA GeForce 8600M GT on 64-bit Lubuntu 12.04 Linux, driver version 295.49. glewinfo shows ARB_debug_output as one of these "OK [MISSING]" extensions. I filed a bug about all of this, referring to someone else's discussion of the GLEW problem. I haven't figured out a fix, or even if it can be fixed with GLEW, and I'm bored worrying about that particular sample code.
So, what I'd like is, an example of ARB_debug_output that actually works / is robust. Meaning working buildable code, not a tutorial. Gracefully handles the (likely!) case that the driver doesn't offer the extension unless hurdles A, B, and C are jumped. I'm currently downloading large 3d engine projects to see if their test suites qualify. Do you know of anything that you're sure works? Then at least I can prove that it's not the driver, this is what's supposed to happen, here's an API stack that actually works in the real world, etc.