Developer Guide for Intel® SDK for OpenCL™ Applications 2017
ID
773042
Date
10/22/2018
Public
A newer version of this document is available. Customers should click here to go to the newest version.
Legal Information
Getting Help and Support
Introducing the Intel® SDK for OpenCL™ Applications
What's New in This Release
Which Version of the Intel® SDK for OpenCL™ Applications Should I Use?
Intel® Code Builder for OpenCL™ API Plug-in for Microsoft Visual Studio*
Intel® Code Builder for OpenCL™ API Plug-in for Eclipse*
Debugging OpenCL™ Kernels on GPU
Intel® SDK for OpenCL™ Applications Standalone Version
OpenCL™ 2.1 Development Environment
Intel® FPGA Emulation Platform for OpenCL™ Getting Started Guide
Troubleshooting Intel® SDK for OpenCL™ Applications Issues
Configuring Microsoft Visual Studio* IDE
Converting an Existing Project into an OpenCL™ Project
OpenCL™ New Project Wizard
Building an OpenCL™ Project
Using OpenCL™ Build Properties
Selecting a Target OpenCL™ Device
Generating and Viewing Assembly Code
Generating and Viewing LLVM Code
Generating Intermediate Program Binaries with Intel® Code Builder for OpenCL™ API Plug-in
Configuring OpenCL™ Build Options
Host and Target Systems are Stuck
Symptom:
The host and target machine seem hung/stuck and never run to completion.
On the host machine, the host application remains in the "Running" state, seems hung/stuck and never runs to completion or hits a breakpoint in the GPU. In addition, the target machine GFX display state seems frozen/hung.
Likely root-cause: missing/broken firewall rule for gdbserver (debug server) traffic on the target machine.
Solution:
- Release the target system: stop your debug session: in Visual Studio go to Debug > Stop Debugging
- Open the Debug Output pane: in Visual Studio go to > Debug > Window > Output. You should see a message similar to the following: INTEL_GT_DEBUGGER: (2696194) Failed to connect to gdbserver at target_hostname:2530.
-
- If there is no line that starts with INTEL_GT_DEBUGGER, this means that you did not enable logging enabled for the GPU kernel debugger. Follow the instructions below to enable logging.
- If you received a message starting with INTEL_GT_DEBUGGER, continue to the next step.
- Open the firewall exceptions page Start > Windows Firewall > Allow an app or feature through Windows Firewall.
- Click the Change Settings button.
Click Allow another app > Browse > Select %INTELGTDEBUGGERROOT%target\bin\gdbserver.exe
NOTE:Usually this is "C:\Program Files\Intel\Debugger for Heterogeneous Compute\target\bin\gdbserver.exe"- Click Add.
- Select the network for which you want it enabled (Consult with your IT expert on the type of network that should be enabled).
- Click OK.
- Try again to connect.
To enable logging for the GPU kernel debugger, do the following:
- Visual Studio > Tools > Intel Code Builder for OpenCL API > OpenCL API Debugger > Options > Kernel Debugger
- Check Log to Output Debug Pane.
- Restart Visual Studio and start a new debug session. Now you should be able to see diagnostics from the GPU Kernel debugger in the output pane.