microsoft / microsoft/vscode-cpptools
VSCode fails to send ctrl-c to arm-none-eabi-gdb
@pieandcakes is already working on this.
Since May 10, 2017.
- Dominant language
- TypeScript
- Stars
- 6.2k
- Forks
- 1.7k
- Avg merge
- 14h 46m
- Merged PRs (30d)
- 61
Description
After some debugging and reading issues such as #328 and #703 it seems to me VSCode fails to send ctrl-c to the arm-none-eabi-gdb process to break the running target.
The workaround discussed in #328 is to add a breakpoint in main(...) for the debugger to halt initially. That works for me and I can single step but if I press RUN and then PAUSE the target is not halted. Halting is still possible by telnetting to localhost 4444 and issuing the haltcommand to OpenOCD. The target is now halted and "debuggable" in VSCode.
If I do all debugging directly in arm-none-eabi-gdb in the terminal everything works file, including breaking with ctrl-c:
^C
Program received signal SIGINT, Interrupt.
I am running Version 1.12.1 (1.12.1) (f6868fce3eeb16663840eb82123369dec6077a9b) in macOS.
Edit: I see the same issue in the exact same version in Linux.
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.