AnsweredAssumed Answered

Problem with hitting breakpoints

Question asked by stenr on Jan 13, 2014
Latest reply on Jan 26, 2014 by urishomroni


I am a newbie on codexl, but I think I have got it to work. Looks promising. My only problem so far, seems related to hitting breakpoints in my .cl files. This means I can successfully add breakpoints at cl-functions, such as clEnqueueNDRangeKernel, using the breakpoints view. Then I can step into my kernel code using F11. I would like to be able to add breakpoints in my .cl code, in order to avoid stepping through for-loops in the kernel code. If I shift+F11 inside a for-loop in the .cl file, I come "on the other side" of the clEnqueueNDRangeKernel breakpoint. Should I add some project settings somewhere, or are there any limitations on the .cl-files or how they are built, in order to get them working in codeXL? The .cl files are added to the VS project.


Btw. .cl breakpoints work in the teapot sample.


I use CodeXL 1.3, OpenCL 1.2, VS2012 and AMD FirePro W7000.


Best Regards,