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
Copy file name to clipboardExpand all lines: Documentation/Debugger/gdb/Windows Subsystem for Linux.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,7 @@ Code can be written on Windows itself using VSCode and debugged through `bash.ex
11
11
*[Visual Studio Code](https://code.visualstudio.com) + Microsoft C/C++ extension for VSCode.
12
12
13
13
##How-To
14
-
To debug, commands will be routed from Windows through`bash.exe` to setup debugging. Because our extension runs as a 32-bit process, it will need to use the`C:\Windows\SysNative` folder to access the executable that is normally in`C:\Windows\System32`. We will be using the`"pipeTransport"` ability within the extension to do debugging and`"sourceFileMap"` to map the source from the subsystem's paths back to Windows path.
14
+
To debug, commands will be routed from Windows through`bash.exe` to setup debugging. Because our extension runs as a 32-bit process, it will need to use the`C:\Windows\SysNative` folder to access the`bash.exe`executable that is normally in`C:\Windows\System32`. We will be using the`"pipeTransport"` ability within the extension to do debugging and`"sourceFileMap"` to map the source from the subsystem's paths back to Windows path.
15
15
16
16
**NOTE: Applications will need to be compiled in the`Windows Subsystem for Linux (WSL)` prior to debugging.**