From 3535bb6b5be66ba3b74f3c61d22459c46f885fdf Mon Sep 17 00:00:00 2001 From: Jorge Aparicio Date: Thu, 21 Jan 2021 13:07:46 +0100 Subject: [PATCH] vs code may automatically switch to the run view --- embedded-workshop-book/src/gdb.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/embedded-workshop-book/src/gdb.md b/embedded-workshop-book/src/gdb.md index 9d6871f..04094c5 100644 --- a/embedded-workshop-book/src/gdb.md +++ b/embedded-workshop-book/src/gdb.md @@ -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