Skip to content

Commit c99daed

Browse files
committed
Correct line numbers referenced in breakpoint section of IDE 2.x debugger tutorial
The screenshots included with the tutorial show breakpoints were placed at lines 33 and 35, yet the text is written as though the second breakpoint is at line 36. Since it is easier to update the text, and since line 35 is a more logical place for the breakpoint, the text is corrected.
1 parent 90d1203 commit c99daed

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

content/software/ide-v2/tutorials/ide-v2-debugger/ide-v2-debugger.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -102,14 +102,14 @@ Once your program has been uploaded, we can start using the debugger.
102102

103103
Let's begin by creating something called a **breakpoint**. Breakpoints are used to stop the program execution at a specific line (or when a specific condition is verified). We can use multiple of these in a program (the number is variable depending on the processor).
104104

105-
In this example, we are going to set a breakpoint for **line 33** and **line 36**. These are set by clicking to the left of the line numbering in the editor.
105+
In this example, we are going to set a breakpoint for **line 33** and **line 35**. These are set by clicking to the left of the line numbering in the editor.
106106

107107
![Navigating the Debugger.](assets/debugger-img03.png)
108108

109109
We can now go through our code, step by step.
110110
The first (automatic) stop will be triggered by the **Debugger** itself, and it will be a standard entry-point, ignore that for now.
111111

112-
Let's continue, by clicking on the **Play/pause** button (**Continue**). The program will now run to the first breakpoint, line 33. If we click it again, it will jump to line 36 (the lines 34 and 35 will still be executed but we won't see that). Clicking the **Play/pause** button again will continue running the program which will pause at its next breakpoint, line 33. We're in the main loop, after all.
112+
Let's continue, by clicking on the **Play/pause** button (**Continue**). The program will now run to the first breakpoint, line 33. If we click it again, it will jump to line 35 (line 34 will still be executed but we won't see that). Clicking the **Play/pause** button again will continue running the program which will pause at its next breakpoint, line 33. We're in the main loop, after all.
113113

114114
![Going between breakpoints.](assets/playpause.gif)
115115

0 commit comments

Comments
 (0)