If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

gDEBugger and APITrace are not equivalent. It's like comparing MS Office to to one of the GTK notepad clones. It's great to have a FOSS solution, but it has years of hard work ahead of it to be even half as useful as gDEBugger (or PIX for D3D users, or Parallel Nsight, etc.).

That said, I'm glad gDEBugger has had a new release. The last release was particularly buggy with GL Core Profile code for me. Hopefully this new version addresses the bugs; will test shortly and find out. Also, bits of the UI in the last stand-alone version were less than ideal (the vertex buffer visualizer didn't allow user-specified vertex layouts, for instance), and the Visual Studio integration was a joke compared to Parallel Nsight or PIX. Granted, for D3D coders, Visual Studio 11 has its own built-in GPU debugging features now. Yet one more bit of developer-friendly polish that Microsoft happily does which the Linux crowd can't or won't take the lead on.

Granted, for D3D coders, Visual Studio 11 has its own built-in GPU debugging features now. Yet one more bit of developer-friendly polish that Microsoft happily does which the Linux crowd can't or won't take the lead on.

I'm not sure i agree with that sentiment. For years Visual Studio was terrible in comparison to various java based IDE's (for non-GL code at least). It's gotten better with each new release, but you still have to buy 3rd party extensions like ReSharper to get many of the tools you would expect.

IDE = crappy text editor I don't want to use, combined with a crappy debugger frontend I don't want to use, combined with a crappy project manager I don't want to use. No exceptions. VS2010 is an abomination still.

Binding something that important to a IDE would be a step backwards, not an improvement.