microsoft / microsoft/vscode-cpptools

In launch.json debugServerPath always be type string,It can't work on PowerShell

Open
#1,812 4 comments 0 reactions 1 assignee View on GitHub

@pieandcakes is already working on this.

Since Apr 10, 2018.

debugger embedded
Dominant language
TypeScript
Stars
6.2k
Forks
1.7k
Avg merge
14h 46m
Merged PRs (30d)
61

Description

CPUs Intel(R) Core(TM) i5-6400 CPU @ 2.70GHz (4 x 2712)
Memory (System) 19.94GB (14.97GB free)
Process Argv F:\Program Files\Microsoft VS Code\Code.exe
Screen Reader no
VM 0%
include-autocomplete ajs 0.0.4
rtf ale 0.3.0
bracket-pair-colorizer Coe 1.0.27
tslint eg2 1.0.28
CppSnippets har 0.0.13
vscode-cudacpp kri 0.1.1
cortex-debug mar 0.1.19
vscode-clang mit 0.2.2
python ms- 2018.3.1
cpptools ms- 0.16.1
makefiles-support-for-vscode nae 0.0.3
cmake twx 0.0.17
cmake-tools vec 0.10.4

In order to debug STM32,I used the opencod on win10 and changed launch.json.
"debugServerPath": "F:\gcc\GNUMCUEclipse\OpenOCD\0.10.0-7-20180123-1217\bin\openocd.exe",
"debugServerArgs": "-f ${workspaceRoot}\st_nucleo_f0.cfg",
But it can't work,the log show like this:

1: (227) Starting: "F:\gcc\GNUMCUEclipse\OpenOCD\0.10.0-7-20180123-1217\bin\openocd.exe" -f G:\FMD\VScode\code\mbed-os-example-blinky\st_nucleo_f0.cfg
1: (20235) <-logout
C disconnect: {"restart":false}

I had try to comments the "debugserverPath" and "debugServerArgs".
Then Run F:\gcc\GNUMCUEclipse\OpenOCD\0.10.0-7-20180123-1217\bin\openocd.exe -f G:\FMD\VScode\code\mbed-os-example-blinky\st_nucleo_f0.cfg on PowerShell before
debug.
Everything is OK.
I think there are something wrong with the debugServerPath in launch.json
The Double quotes case it can't work on powershell.

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.