Timeline for How can I debug GLSL shaders?
Current License: CC BY-SA 3.0
14 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 15, 2021 at 11:47 | comment | added | pmw1234 | The vulkan SDK provides a printf for shader debugging, I haven't had the need to use it so I'll just post this as a comment. Here is a link:github.com/KhronosGroup/Vulkan-ValidationLayers/blob/master/… | |
| Oct 1, 2019 at 2:32 | comment | added | wip | Here's a debugging method I suggested to a related question: stackoverflow.com/a/29816231/758666 | |
| Mar 7, 2018 at 22:11 | answer | added | SpaceKees | timeline score: 3 | |
| Jun 26, 2016 at 15:07 | answer | added | Ruslan | timeline score: 3 | |
| Jan 22, 2016 at 14:59 | answer | added | Nobody moving away from SE | timeline score: 9 | |
| Aug 31, 2015 at 12:17 | vote | accept | Martin Ender | ||
| Aug 7, 2015 at 18:39 | answer | added | Sepehr | timeline score: 11 | |
| Aug 7, 2015 at 13:14 | answer | added | cifz | timeline score: 34 | |
| Aug 7, 2015 at 12:00 | comment | added | cifz | gDEBugger is extremely old and not supported since a while. If you are looking from frame and GPU state analysis you this is other question is strongly related: computergraphics.stackexchange.com/questions/23/… | |
| Aug 7, 2015 at 11:57 | comment | added | Bert | I've never done any WebGL programming and hence I'm not familiar with WebGL- Inspector. With gDEBugger you can at least inspect the entire state of your shader pipeline including texture memory, vertex data, etc. Still, no actual stepping through code afaik. | |
| Aug 7, 2015 at 11:47 | comment | added | Martin Ender | @Bert Hm yeah, I guess gDEBugger is the OpenGL equivalent to WebGL-Inspector? I've used the latter. It's immensely useful, but it's definitely more debugging OpenGL calls and state changes than shader execution. | |
| Aug 7, 2015 at 11:06 | comment | added | Bert | Have you looked into gDEBugger? Quoting the site: "gDEBugger is an advanced OpenGL and OpenCL Debugger, Profiler and Memory Analyzer. gDEBugger does what no other tool can - lets you trace application activity on top of the OpenGL and OpenCL APIs and see what is happening within the system implementation." Granted, no VS style debugging/stepping through code, but it might give you some insight in what your shader does (or should do). Crytec released a similar tool for Direct shader "debugging" called RenderDoc (free, but strictly for HLSL shaders, so maybe not relevant for you). | |
| Aug 7, 2015 at 9:39 | answer | added | S.L. Barth is on codidact.com | timeline score: 5 | |
| Aug 7, 2015 at 8:24 | history | asked | Martin Ender | CC BY-SA 3.0 |