File tree Expand file tree Collapse file tree 2 files changed +11
-3
lines changed Expand file tree Collapse file tree 2 files changed +11
-3
lines changed Original file line number Diff line number Diff 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
You can’t perform that action at this time.
0 commit comments