Points: breakpoint, watch, Point, clear
Breakpoints and watchpoints as Point objects with state and removal.
since 0.1.0-rc.1since 0.3.0
Methods
| Entry | Signature | Available since | API 3 |
|---|---|---|---|
breakpoint | breakpoint(location, temporary=False, *, condition=None, ignore_count=0) -> Point | 0.1.0-rc.1 | unchanged |
watch | watch(path) -> Point | 0.3.0 | unchanged |
Point | Point: active, hit_count, condition; enable(), disable(), remove(), with | 0.3.0 | unchanged |
clear | clear() -> None | 0.1.0-rc.1 | unchanged |
API 3 changes (0.5.0)
Unchanged; a point condition is evaluated without function calls.
Recommended
watch and breakpoint inside a with block or with an explicit remove().
with t.watch("app_state.ticks"):
t.resume()
point = t.breakpoint("board_led_toggle")
t.reach("app_loop")
t.check("point is active", point.active, True)
point.remove()Avoid
gdb.execute("break …") bypasses Target: the point is neither tracked nor removed. clear() also removes fault guards — only on purpose.
import gdb
gdb.execute("break board_led_toggle") # not tracked, not cleaned up
t.clear() # also removes fault guardsThe fragments show refused or discouraged patterns, not a working recipe.
Fragments for a scenario body; firmware symbols are illustrative.