microsoft / microsoft/vscode-cpptools
gdb needs to be manually killed after end of debug session
@pieandcakes ci sta già lavorando.
Dal 13/7/2017.
- Lingua principale
- TypeScript
- Stelle
- 6.2k
- Fork
- 1.7k
- Merge medio
- 14h 46m
- PR unite (30g)
- 61
Descrizione
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.
Guida per i contributori
Apri la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Valutazione
Questa issue non è ancora stata valutata.