OpenCL：Cloo没有看到API调试器 [英] OpenCL: Cloo does not see API debugger

问题描述

我使用一个名为CLoo的C＃包装器来使用OpenCL API。我使用的openCL平台是英特尔CPU。



当我运行官方英特尔示例代码（C / C ++应用程序）时，然后在VS2010中使用IntelOpenCL插件窗口（工具/ Cod builder-OpenCL Debugger）我可以看到命令队列，API调用历史等等。所以主机端API调试工作正常。内核调试也有效。



当我对CLoo执行相同操作时，我只能调试内核，而不能调试主机端API。我打开了内核调试chekcbox（工具/代码生成器 - 选项/基本设置/启用OpenCL内核调试）以及主机端API调试（工具/代码生成器 - 选项/ API调试器/启用OpenCL API Debuger）。 />


对于我在调用第一个OpenCL API函数（clGetPlatformIDs）时看到的Intel C / C ++示例，我的应用程序和VS Intel打开了一个端口（56202） OpenCL插件连接到它。

我也注意到上下文是创建然后另一个端口被我的应用程序打开（56203）并且VS连接到它。这必须是内核调试端口。



我的问题是当我用Cloo调用第一个OpenCL API调用（clGetPlatformIDs）时为什么它不打开API调试器端口对于C / C ++应用程序。



作为一种解决方法，我发现可以通过使用环境变量打开日志记录，但它不如VS插件方便会是。

INTEL_OCL_DBG_LOG = 1

INTEL_OCL_DBG_LOG_FILE = c：\ temp\debugger.txt

I usie a C# wrapper called CLoo to use the OpenCL API. The openCL platform I use is the Intel CPU.

When I run the official Intel sample code (a C/C++ application) then in the VS2010 IntelOpenCL plugin windows (Tools/Cod builder-OpenCL Debugger) I can see the command queue, the API call history etc. So the host side API debugging works. The kernel debugging works too.

When I do the same with CLoo then I can only debug the kernel, but not the host side API. I turned on both the kernel debugging chekcbox (Tools/Code Builder-Options/Basic Settings/Enable OpenCL Kernel Debugging) and also the host side API debugging (Tools/Code Builder-Options/API Debugger/Enable OpenCL API Debuger).

For the Intel C/C++ sample I have seen when I call the first OpenCL API function (clGetPlatformIDs) then a port is opened (56202) by my application and the VS Intel OpenCL plugin connects to it.
I also noticed then the context is create then another port is opened (56203) up by my application and VS connects to it. This must be the kernel debugging port.

My question is when I call the first OpenCL API call (clGetPlatformIDs) with Cloo why does it not open the API debugger port as for the C/C++ application.

As a workaround I have found that one can turn on the logging by using environment variables, but it is not as convenient as VS plugins would be.
INTEL_OCL_DBG_LOG=1
INTEL_OCL_DBG_LOG_FILE=c:\temp\debugger.txt

推荐答案

使用 CLoo支持链接 [ ^ ]。

这篇关于OpenCL：Cloo没有看到API调试器的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！