You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Sample debug instructions
Adding in debug instructions for one README. Once this PR is approved, I will add in the same instruction to all sample README files.
* Repositioned debugging
I removed the Debug section since it was out of place.
Looking at the VS code section, the link for learning more about the extensions is also valid for the launch configurations extension, so I added a bullet to the "Using VS Code" steps to include using the GDB.
Copy file name to clipboardExpand all lines: DirectProgramming/C++/CombinationalLogic/MandelbrotOMP/README.md
+4-1Lines changed: 4 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -50,12 +50,15 @@ The basic steps to build and run a sample using VS Code include:
50
50
- Configure the oneAPI environment with the extension **Environment Configurator for Intel oneAPI Toolkits**.
51
51
- Open a Terminal in VS Code (**Terminal>New Terminal**).
52
52
- Run the sample in the VS Code terminal using the instructions below.
53
+
- (Linux only) Debug your GPU application with GDB for Intel®
54
+
oneAPI toolkits using the **Generate Launch Configurations** extension.
53
55
54
-
To learn more about the extensions and how to configure the oneAPI environment, see
56
+
To learn more about the extensions, see
55
57
[Using Visual Studio Code with Intel® oneAPI Toolkits](https://software.intel.com/content/www/us/en/develop/documentation/using-vs-code-with-intel-oneapi/top.html).
56
58
57
59
After learning how to use the extensions for Intel oneAPI Toolkits, return to this readme for instructions on how to build and run a sample.
0 commit comments