oneapi-src / oneapi-src/oneAPI-samples

IntelGfxDbgPackage did not load correctly in vs2019

Open
#1,370 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

question
Dominant language
C++
Stars
1.2k
Forks
745
PR merge metrics
No merged PRs in 30d

Description

1 My computer configuration
OS: win10
processor: 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz 2.42 GHz
graphics card: Intel(R) Iris(R) Xe Graphics
memory: 16G
vistual studio: 2019
cmake:3.26-rc3

2 install
I downloaded w_BaseKit_p_2023.0.0.25940_offline.exe and followed this to install, and I installed graphics drivers

3 run
I followed this to run

4 What did I get
After I opened vs2019 I got error dialog saying IntelGfxDbgPackage did not load correctly, I closed this error dialog and selected Extensions > Intel > Browse an Intel oneAPI Sample > vector add, but found the Debug > Start Without Debugging is gray and un-clickable.

5 My question
Does my computer support oneapi? If so, why cannot I run the sample, do I forget install or config sth?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the linked oneAPI sample-project steps in Visual Studio 2019 with the reported Windows, Intel graphics, and CMake setup. Check when IntelGfxDbgPackage fails to load and why Debug > Start Without Debugging is disabled; done means identifying the required support or configuration and documenting the resolution.

Written by the indexing model from the issue text.

Assessment

Tech stack
cmake, cpp
Domain
build-system, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.