microsoft / microsoft/vscode-cpptools
gdb needs to be manually killed after end of debug session
@pieandcakes is already working on this.
Since Jul 13, 2017.
- Dominant language
- TypeScript
- Stars
- 6.2k
- Forks
- 1.7k
- Avg merge
- 14h 46m
- Merged PRs (30d)
- 61
Description
Setup
Most recent stable VSCode version debugging ARM Cortex M4 code using arm-none-eabi-gdb connected to JLinkGDBServer as gdbserver
Affected OS
MacOS (tested on ElCapitan, Sierra, High Sierra), Linux (tested on Ubuntu 16.10 and 17.04)
Windows (tested on Windows 10) is unaffected by this issue
What's wrong
First debug session goes fine. After disconnecting from debug or restarting no more debug sessions are possible. In case of restart debug session ends but the new one is not started.
Also breakpoints on Linux and MacOS are broken, code execution stops at main but that's it.
Manual debug session ran from terminal works as expected so it's most likely VSCode related issue.
Workaround
arm-none-eabi-gdb process must be manually killed from terminal after each debug session. Alternatively on Linux unnamed empty window that pops under VSCode window may be closed. This allows next debug session to proceed but must be repeated every time.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.