Skip to content

Commit ce1b730

Browse files
authored
Added more information about data breakpoints. (#529)
1 parent cc6287f commit ce1b730

File tree

2 files changed

+11
-3
lines changed

2 files changed

+11
-3
lines changed

README.md

Lines changed: 11 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -196,9 +196,17 @@ name. Function breakpoints are shown with a red triangle in the **BREAKPOINTS se
196196

197197
##### Data breakpoints
198198

199-
If a debugger supports data breakpoints, they can be set from the context menu in the **VARIABLES section**. The Break
200-
on Value Change/Read/Access commands add a data breakpoint that is hit when the value of the underlying variable
201-
changes/is read/is accessed. Data breakpoints are shown with a red hexagon in the **BREAKPOINTS section**.
199+
If a debugger supports data breakpoints, they can be set from the context menu of a variable in the **WATCH section**.
200+
The Break on Value Change/Read/Access commands add a data breakpoint that is hit when the value of the underlying
201+
variable changes/is read/is accessed. Data breakpoints are shown with a red hexagon in the **BREAKPOINTS section**.
202+
203+
![Creating a data breakpoint](https://github.com/Open-CMSIS-Pack/vscode-cmsis-debugger/raw/main/images/data-breakpoint.gif)
204+
205+
> 📝 **Note:**
206+
>
207+
> When hitting a data breakpoint, the program execution does not stop exactly on that line of code. Depending on the
208+
> underlying CPU architecture, stopping can be delayed by up to 5 cycles. Use the
209+
> [Call Stack](#call-stack) view to determine what caused the execution to stop.
202210
203211
##### Logpoints
204212

images/data-breakpoints.gif

2.1 MB
Loading

0 commit comments

Comments
 (0)