- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The title says it all; the application works fine otherwise if the Inspector is not attached. We are using II integrated with Visual Studio 2017. Linker set to a Full debug info output.
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi RafalS,
Thanks for the sharing the sighting.
Can you supply this system information here.
Also what version of Intel® Inspector is in use? What version of Intel® Graphics Driver or Which version of Intel® CPU Runtime for OpenCL™ Applications is in use?? What version of Visual Studio 2017?
The easiest way to determine graphics driver is by looking at device manager->display adapters, right click, properties, driver, driver version to get a version.
Can you supply a minimally representative source code reproducer? if so, please only share source code that is privileged to share. What device is clBuildProgram(...) targeting? Did the same behavior occur if targeting both CPU and iGFX (assuming the system has both available). Was clBuildProgram(...) targeting something non-intel?
To make it easy, if you can share the project we can take a look at the build parameters... This could be shared via private message if necessary. If I can reproduce, we can file it to the inspector team.
Thanks,
-MichaelC
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page