From 88b1bef671980436d7c9c3cb9992cf5043d8a87a Mon Sep 17 00:00:00 2001 From: RKopsch <40633808+rkopsch@users.noreply.github.com> Date: Tue, 6 May 2025 13:14:00 +0200 Subject: [PATCH] Update debug_views.md Grammarly Check --- docs/debug_views.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/debug_views.md b/docs/debug_views.md index 8128c45e..1d043712 100644 --- a/docs/debug_views.md +++ b/docs/debug_views.md @@ -151,7 +151,7 @@ To add a condition to an existing breakpoint: #### Triggered breakpoints A triggered breakpoint is type of conditional breakpoint that is enabled once another breakpoint is hit. They can be useful -when diagnosing failure cases in code that happen only after a certain precondition. +when diagnosing failure cases in code that happens only after a certain precondition. Triggered breakpoints can be set by right-clicking on the glyph margin, selecting **Add Triggered Breakpoint**, and then choosing which other breakpoint enables the breakpoint. @@ -163,7 +163,7 @@ choosing which other breakpoint enables the breakpoint. Inline breakpoints are only hit when the execution reaches the column associated with the inline breakpoint. This is useful when debugging minified code, which contains multiple statements in a single line. -An inline breakpoint can be set using **Shift + F9** or through the context menu during a debug session. Inline breakpoint +An inline breakpoint can be set using **Shift + F9** or through the context menu during a debug session. Inline breakpoints are shown inline in the editor. Inline breakpoints can also have conditions. Editing multiple breakpoints on a line is possible through the context menu in @@ -268,4 +268,4 @@ closing of quotes, and other language features. The following example shows how to check the currently set breakpoints with the `> info break` command. Afterwards, the application is run with the `> continue` command. -![Entering GDB commands in the Debug Console REPL](./images/entering_gdb_commands.gif) \ No newline at end of file +![Entering GDB commands in the Debug Console REPL](./images/entering_gdb_commands.gif)