Hi.
During visual studio code builder debugging, I have a clEnqueueNDRangeKernel failing for a certain kernel, with a bad memory access. To find out which work item (of 512) is causing the error, I have had to gradually (and awkwardly) limit the participating work items, until I find the item(s) that are requesting this bad access. I find myself in this position reasonably often: is there a more graceful way to do this?