Posted by Demoscene Passivist on Jan 23, 2011; 5:32pm
URL: https://forum.jogamp.org/problems-with-shaders-tp2092883p2314564.html

I came back to the issue of glGetProgramInfoLog vs. glGetObjectParameterivARB today. I tried to debug a fragment shader wich was working fine on ATI hardware but was completely broken on NVidia.

As I dug further into the issue I noticed that I got nearly no debug output (only glerror messages) from the nvidia machine wich output was generally way more detailed before I switched to using glGetProgramInfoLog as suggested by julien.

After I switched back to glGetObjectParameterivARB I got a very detailled debug/error output from the NVidia driver.

So it seems either glGetProgramInfoLog is broken in JOGL or this is some kind of strange driver behavior on NVidia or I'am too stupid to understand a subtile difference between glGetProgramInfoLog  and glGetObjectParameterivARB ... . Maybe some else can shed light on this issue ...