AnsweredAssumed Answered

All variables are zero when stopped at a gDEBugger breakpoint

Question asked by djibi2 on Apr 30, 2012

I'm new to the gDEBugger and seem to be doing something fundamentally wrong.  When I run the debugger is shows all values in the "locals" window as zero ( same thing in the Multi-watch Data view).    After having this trouble with my own app I ran the Teapot demo that came with the debugger and am having the same results.

 

I'm running on Window 7 with the new standalone debugger (6.2.865).  I set breakpoint  for the cl EnqueueNDRangeKernel call.  The execution stops, and I can single step through the code but I don't see any non-zero values for the variables. 

 

Thanks

Outcomes