Skip to content

Update debug_views.md #212

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
May 12, 2025
Merged

Update debug_views.md #212

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
88b1bef
Update debug_views.md
rkopsch May 6, 2025
6afe72f
Merge branch 'main' into patch-5
jreineckearm May 6, 2025
e357e66
Merge branch 'main' into patch-5
jreineckearm May 12, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions docs/debug_views.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Copy link
Collaborator

@jreineckearm jreineckearm May 6, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
when diagnosing failure cases in code that happens only after a certain precondition.
when diagnosing failure cases in code that happen only after a certain precondition.

I think the original version is correct. Refers to cases, not code.


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.
Expand All @@ -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
Expand Down Expand Up @@ -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)
![Entering GDB commands in the Debug Console REPL](./images/entering_gdb_commands.gif)
Loading