- Debugger still does not work for me, it locks up Visual Studio, CodeXL crashes inside clBuildProgram. The same program runs fine normally. I read somewhere that the previous version had problems with the latest radeon drivers, is it still the case?
- Visual Studio 2013 integration can hardly scroll any views, they only update in every 10 seconds, completely unusable.
- Could not send the crash report of CodeXL, not using proxy.
Which driver release are you working with? CodeXL 1.5 supports driver releases up to 14.10 and from 14.30 (unreleased yet) onward. If you're using driver 14.20 (bundled in Catalyst 14.7) then Kernel Debugging will not work.
Visual Studio 2013 performs a registration step of the CodeXL extension after the CodeXL installation is complete. This may take a few steps and slows down the PC considerably. Can you try CodeXL inside VS2013 again? What type of file are you scrolling?
Can you attach the crash report? Or send it to email@example.com?
Just installed it again, after putting back the old version temporarily, and visual studio fixed itself.
I am using 14.7, the beta, going to try it with the non-beta in a minute.
Update: Had to reinstall codexl again, visual studio kept closing itself without a trace after 10 seconds opening the project. But everything seems fine now, debugging works with the non-beta driver. I'm so happy, had to rely on printf for the first few weeks of my opencl adventures.
I'm also having trouble with the Visual Studio plugin views refreshing too slowly.
This is on VS2012 pro, in an Application Timeline Trace window, with a fresh installation of CodeXL 1.5.6571.0 . The issue persists even after restarting Visual Studio. Both the upper timeline view and the summary display below it exhibit this behaviour. The detailed popup on kernels in the timeline view flickers, even though I'm not moving my mouse at all.
Edit: CodeXL in stand-alone mode does not have the display refresh issues.
It was said that those problems will be fixed in the new CodeXL release. Well they are not!
Can't debug because of access violations in clBuildProgram like the OP already mentioned. Profiling doesn't work because I immediatly get a bluescreen when the applications starts.
Please fix this and please don't let us wait for another scheduled release and just publish a fixed version.
- Windows 7 x64
- Latest (non beta) drivers installed
Not trying to dodge our responsibility for a robust CodeXL user experience, but crashes inside clBuildProgram indicate a problem in the OpenCL runtime or compiler, both of which are packaged in Catalyst and are unchanged by a CodeXL installation. CodeXL forces a few compilation flags to support kernel debugging. This is why a kernel may build properly when run outside CodeXL but cause a crash when run in a CodeXL debug session.
The AMD Developer Tools team works closely together with the OpenCL runtime and compiler teams to resolve these issues. However, to benefit from these fixes you have to install the Catalyst release that contains them.
The next Catalyst release is very near and I hope it will allow you to debug your kernels with CodeXL. Please let us know if it fails to do so.
I'm having some issues with this version of CodeXL and Visual Studio too, just installed Catalyst Omega and I can debug kernels and everything, but, when I try to watch some variables like int4, float4, or lets say, view the content of a float4 p, p.x, Visual Studio lock down and only unlock closing the debugging program instance. This is very annoying, I'm actually stuck on a kernel because I can't debug it.