mirror of
https://github.com/ferrous-systems/embedded-trainings-2020.git
synced 2025-01-08 15:25:33 +00:00
vs code may automatically switch to the run view
This commit is contained in:
parent
afcf7ab134
commit
3535bb6b5b
1 changed files with 6 additions and 6 deletions
|
@ -52,12 +52,12 @@ For this tutorial, we'll be using the `beginner/` applications, so let's modify
|
|||
|
||||
[![GDB session within VS code using the cortex-debug extension](code-gdb.png)](./code-gdb.png)
|
||||
|
||||
You are now in a GDB session. Switch to the "Run" view (4th icon from the top on the left sidebar)
|
||||
and you'll see debug information like the call stack, local variables, breakpoints and CPU registers
|
||||
on the left side. On the bottom panel, you can switch to the "Debug console" to issue commands to
|
||||
the GDB server. Near the top of the GUI you'll find a row of buttons to navigate through the program
|
||||
(step, continue, etc.). Breakpoints can be added by clicking to the left of line numbers in the file
|
||||
view.
|
||||
You are now in a GDB session. Switch to the "Run" view (4th icon from the top on the left sidebar),
|
||||
if VS code didn't automatically switch to it, and you'll see debug information like the call stack,
|
||||
local variables, breakpoints and CPU registers on the left side. On the bottom panel, you can switch
|
||||
to the "Debug console" to issue commands to the GDB server. Near the top of the GUI you'll find a
|
||||
row of buttons to navigate through the program (step, continue, etc.). Breakpoints can be added by
|
||||
clicking to the left of line numbers in the file view.
|
||||
|
||||
## Debugging a different program
|
||||
|
||||
|
|
Loading…
Reference in a new issue