Lines Matching full:watchpoint
2652 difficult or impossible to set a breakpoint, or watchpoint, on an
2715 A "watchpoint" is a special breakpoint that stops your program when
2721 can manage a watchpoint like any other breakpoint: you enable, disable,
2736 GDB assigns a number to each breakpoint, watchpoint, or catchpoint
2894 about the specified breakpoint(s) (or watchpoint(s) or
2901 Breakpoint, watchpoint, or catchpoint.
3115 You can use a watchpoint to stop execution whenever the value of an
3131 You can set a watchpoint on an expression even if the expression can
3132 not be evaluated yet. For instance, you can set a watchpoint on
3152 Set a watchpoint for an expression. GDB will break when the
3165 Ordinarily a watchpoint respects the scope of variables in EXPR
3174 Set a watchpoint that will break when the value of EXPR is read by
3178 Set a watchpoint that will break when EXPR is either read from or
3187 which will never change. GDB refuses to create a watchpoint that
3193 Watchpoint 1: *(int *) 6293584
3195 GDB sets a "hardware watchpoint" if possible. Hardware watchpoints
3198 hardware watchpoint, it sets a software watchpoint, which executes more
3221 Hardware watchpoint NUM: EXPR
3223 if it was able to set a hardware watchpoint.
3233 Expression cannot be implemented with read/access watchpoint.
3235 Sometimes, GDB cannot set a hardware watchpoint because the data
3236 type of the watched expression is wider than what a hardware watchpoint
3251 Hardware watchpoint NUM: Could not insert watchpoint
3278 only limited usefulness. If GDB creates a software watchpoint, it
3287 *Note set remote hardware-watchpoint-limit::.
3518 It is often necessary to eliminate a breakpoint, watchpoint, or
3566 Rather than deleting a breakpoint, watchpoint, or catchpoint, you might
3580 A breakpoint, watchpoint, or catchpoint can have any of four
3647 since a watchpoint is inspecting the value of an expression anyhow--but
3648 it might be simpler, say, to just set a watchpoint on a variable name,
3674 watchpoint, or catchpoint number BNUM. After you set a condition,
3735 You can give any breakpoint (or watchpoint or catchpoint) a series of
3751 watchpoint, or catchpoint set (not to the breakpoint most recently
3825 not be possible to access the context where the watchpoint is
14295 `set remote hardware-watchpoint-limit LIMIT'
14384 `write-watchpoint' `Z2' `watch'
14385 `read-watchpoint' `Z3' `rwatch'
14386 `access-watchpoint' `Z4' `awatch'
16003 Hardware breakpoints/watchpoint triggers can be set using:
16021 Set hardware watchpoint on combination of Load/Store Effective
16073 in hardware simple hardware watchpoint conditions of the form:
16079 pattern in a condition expression, and the created watchpoint uses one
19946 the breakpoint, or an expression that defines a watchpoint. The
19948 in the case of a watchpoint, by the `watch' command. The optional
19956 optional WP_CLASS argument defines the class of watchpoint to
19957 create, if TYPE is `BP_WATCHPOINT'. If a watchpoint class is not
19985 The available watchpoint types represented by constants are defined
19989 Read only watchpoint.
19992 Write only watchpoint.
19995 Read/Write watchpoint.
20002 watchpoint scope, the watchpoint remains valid even if execution
20003 of the inferior leaves the scope of that watchpoint.
20059 Watchpoint breakpoint.
20062 Hardware assisted watchpoint.
20065 Hardware assisted read watchpoint.
20068 Hardware assisted access watchpoint.
20078 location (that is, it is a watchpoint) the attribute's value is
20084 expression (the breakpoint is not a watchpoint) the attribute's
21551 `watchpoint-trigger'
21552 A watchpoint was triggered.
21554 `read-watchpoint-trigger'
21555 A read watchpoint was triggered.
21557 `access-watchpoint-trigger'
21558 An access watchpoint was triggered.
21566 `watchpoint-scope'
21567 A watchpoint has gone out of scope.
22220 type of the breakpoint: `breakpoint' or `watchpoint'
22300 Create a watchpoint. With the `-a' option it will create an
22301 "access" watchpoint, i.e., a watchpoint that triggers either on a read
22303 watchpoint created is a "read" watchpoint, i.e., it will trigger only
22305 the options, the watchpoint created is a regular watchpoint, i.e., it
22320 Setting a watchpoint on a variable in the `main' function:
22329 *stopped,reason="watchpoint-trigger",wpt={number="2",exp="x"},
22335 Setting a watchpoint on a variable local to a function. GDB will
22337 value, then for the watchpoint going out of scope.
22346 *stopped,reason="watchpoint-trigger",
22355 *stopped,reason="watchpoint-scope",wpnum="5",
22363 program execution. Note that once the watchpoint goes out of scope, it
22382 bkpt={number="2",type="watchpoint",disp="keep",
22388 *stopped,reason="watchpoint-trigger",wpt={number="2",exp="C"},
22406 bkpt={number="2",type="watchpoint",disp="keep",
22411 ^done,reason="watchpoint-scope",wpnum="2",
23984 command is creating a watchpoint from a variable object.
26243 The program hit watchpoint number NUMBER.
28551 `watchpoint'
28552 Normal, explicitly set watchpoint.
28828 hardware breakpoint or watchpoint, and when the inferior triggers
28829 a hardware-assisted breakpoint or watchpoint.
29105 insert breakpoint or watchpoint packet::).
29525 Insert (`Z') or remove (`z') a TYPE breakpoint or watchpoint
29528 Each breakpoint and watchpoint packet TYPE is documented
29532 for an unrecognized breakpoint or watchpoint packet TYPE. A
29590 Insert (`Z2') or remove (`z2') a write watchpoint at ADDR. KIND
29605 Insert (`Z3') or remove (`z3') a read watchpoint at ADDR. KIND is
29620 Insert (`Z4') or remove (`z4') an access watchpoint at ADDR. KIND
29687 The packet indicates a watchpoint hit, and R is the data
38510 * watchpoint annotation: Annotations for Running.
38792 Ref: set remote hardware-watchpoint-limit587214
39006 Ref: insert breakpoint or watchpoint packet1129080
