Lines Matching full:breakpoint
504 `m4_changequote', so we set a breakpoint there with the GDB `break'
508 Breakpoint 1 at 0x62f4: file builtin.c, line 879.
521 To trigger the breakpoint, we call `changequote'. GDB suspends
527 Breakpoint 1, m4_changequote (argc=3, argv=0x33c70)
1251 a breakpoint on a subroutine whose name begins with `make_', but when
1282 by argument type). For example, when you want to set a breakpoint you
1650 breakpoint at the beginning of the main procedure and then invoking
1659 temporary breakpoint will remain to halt execution.
2011 breakpoint settings).
2309 breakpoint conditional expressions, command scripts, and so forth.
2417 child process will run unimpeded. If you have set a breakpoint in any
2495 `exec', GDB executes the new target up to the first breakpoint in the
2496 new target. If you have a breakpoint set on `main' in your original
2497 program, the breakpoint will also be set on the child process's `main'.
2589 is assigned a small integer id, similar to a breakpoint id.
2652 difficult or impossible to set a breakpoint, or watchpoint, on an
2677 as a signal, a breakpoint, or reaching a new line after a GDB command
2701 A "breakpoint" makes your program stop whenever a certain point in the
2702 program is reached. For each breakpoint, you can add conditions to
2715 A "watchpoint" is a special breakpoint that stops your program when
2721 can manage a watchpoint like any other breakpoint: you enable, disable,
2725 automatically whenever GDB stops at a breakpoint. *Note Automatic
2728 A "catchpoint" is another special breakpoint that stops your program
2733 other breakpoint. (To stop when your program receives a signal, use the
2736 GDB assigns a number to each breakpoint, watchpoint, or catchpoint
2739 breakpoints you use the breakpoint number to say which breakpoint you
2740 want to change. Each breakpoint may be "enabled" or "disabled"; if
2744 A breakpoint range is either a single breakpoint number, like `5', or
2746 `5-7'. When a breakpoint range is given to a command, all breakpoints
2757 * Break Commands:: Breakpoint command lists
2760 * Breakpoint-related Warnings:: ``Breakpoint address adjusted...''
2770 breakpoint you've set most recently; see *note Convenience Variables:
2775 Set a breakpoint at the given LOCATION, which can specify a
2778 specify a LOCATION.) The breakpoint will stop your program just
2786 It is also possible to insert a breakpoint that will stop the
2789 breakpoint.
2792 When called without any arguments, `break' sets a breakpoint at
2798 `finish' does not leave an active breakpoint. If you use `break'
2805 this, you would be unable to proceed past a breakpoint without
2806 first disabling the breakpoint. This rule applies whether or not
2807 the breakpoint already existed when your program stopped.
2810 Set a breakpoint with condition COND; evaluate the expression COND
2811 each time the breakpoint is reached, and stop only if the value is
2815 for more information on breakpoint conditions.
2818 Set a breakpoint enabled only for one stop. ARGS are the same as
2819 for the `break' command, and the breakpoint is set in the same
2820 way, but the breakpoint is automatically deleted after the first
2825 Set a hardware-assisted breakpoint. ARGS are the same as for the
2826 `break' command and the breakpoint is set in the same way, but the
2827 breakpoint requires hardware support and some target hardware may
2829 debugging, so you can set a breakpoint at an instruction without
2834 debug registers. However the hardware breakpoint registers can
2842 hardware-breakpoint-limit::.
2845 Set a hardware-assisted breakpoint enabled only for one stop. ARGS
2846 are the same as for the `hbreak' command and the breakpoint is set
2848 breakpoint is automatically deleted after the first time your
2850 breakpoint requires hardware support and some target hardware may
2856 REGEX. This command sets an unconditional breakpoint on all
2860 or make them conditional the same way as any other breakpoint.
2894 about the specified breakpoint(s) (or watchpoint(s) or
2895 catchpoint(s)). For each breakpoint, following columns are
2901 Breakpoint, watchpoint, or catchpoint.
2904 Whether the breakpoint is marked to be disabled or deleted
2912 Where the breakpoint is in your program, as a memory address.
2913 For a pending breakpoint whose address is not yet known, this
2914 field will contain `<PENDING>'. Such breakpoint won't fire
2916 by breakpoint is loaded. See below for details. A
2917 breakpoint with several locations will have `<MULTIPLE>' in
2921 Where the breakpoint is in the source for your program, as a
2922 file and line number. For a pending breakpoint, the original
2923 string passed to the breakpoint command will be listed as it
2927 If a breakpoint is conditional, `info break' shows the condition on
2928 the line following the affected breakpoint; breakpoint commands,
2929 if any, are listed after that. A pending breakpoint is allowed to
2932 pending breakpoint to resolve to a valid location.
2934 `info break' with a breakpoint number N as argument lists only
2935 that breakpoint. The convenience variable `$_' and the default
2937 the last breakpoint listed (*note Examining Memory: Memory.).
2939 `info break' displays a count of the number of times the breakpoint
2941 `ignore' command. You can ignore a large number of breakpoint
2942 hits, look at the breakpoint info to see how many times the
2943 breakpoint was hit, and then run again, ignoring one less than
2945 breakpoint.
2952 It is possible that a breakpoint corresponds to several locations in
2964 In all those cases, GDB will insert a breakpoint at all the relevant
2967 A breakpoint with multiple locations is displayed in the breakpoint
2969 breakpoint location. The header row has `<MULTIPLE>' in the address
2973 BREAKPOINT-NUMBER.LOCATION-NUMBER.
2978 1 breakpoint keep y <MULTIPLE>
2980 breakpoint already hit 1 time
2985 BREAKPOINT-NUMBER.LOCATION-NUMBER as argument to the `enable' and
2988 locations that belong to their parent breakpoint (with the `delete NUM'
2989 command, where NUM is the number of the parent breakpoint, 1 in the
2990 above example). Disabling or enabling the parent breakpoint (*note
2992 breakpoint.
2994 It's quite common to have a breakpoint inside a shared library.
2997 updates breakpoint locations whenever any shared library is loaded or
2998 unloaded. Typically, you would set a breakpoint in a shared library at
3001 you try to set breakpoint, GDB will ask you if you want to set a so
3002 called "pending breakpoint"--breakpoint whose address is not yet
3008 breakpoint, that breakpoint is resolved and becomes an ordinary
3009 breakpoint. When a library is unloaded, all breakpoints that refer to
3013 example, if you have a breakpoint in a C++ template function, and a
3015 new location is added to the list of locations for the breakpoint.
3019 enable and disable them and perform other breakpoint operations.
3022 when the `break' command cannot resolve breakpoint address
3025 `set breakpoint pending auto'
3026 This is the default behavior. When GDB cannot find the breakpoint
3027 location, it queries you whether a pending breakpoint should be
3030 `set breakpoint pending on'
3031 This indicates that an unrecognized breakpoint location should
3032 automatically result in a pending breakpoint being created.
3034 `set breakpoint pending off'
3036 unrecognized breakpoint location results in an error. This
3039 `show breakpoint pending'
3043 Once breakpoint is set, it will be automatically updated as shared
3048 breakpoint address is read-only or read-write. This applies to
3056 `set breakpoint auto-hw on'
3057 This is the default behavior. When GDB sets a breakpoint, it will
3059 breakpoint must be used.
3061 `set breakpoint auto-hw off'
3062 This indicates GDB should not automatically select breakpoint
3064 trying to set software breakpoint at a read-only address.
3067 the breakpoint address with a special instruction, which, when
3073 removing breakpoint can reduce the performance. This behavior can be
3076 `set breakpoint always-inserted off'
3081 `set breakpoint always-inserted on'
3083 If the user adds a new breakpoint, or changes an existing
3084 breakpoint, the breakpoints in the target are updated immediately.
3085 A breakpoint is removed from the target only when breakpoint
3088 `set breakpoint always-inserted auto'
3091 `breakpoint always-inserted' mode is on. If GDB is controlling
3092 the inferior in all-stop mode, GDB behaves as if `breakpoint
3117 this may happen. (This is sometimes called a "data breakpoint".) The
3217 hardware-breakpoint-limit::.
3229 currently. If GDB finds that it is unable to set a hardware breakpoint
3262 kind of breakpoint or the call completes.
3271 doing that would be to set a code breakpoint at the entry to the `main'
3477 or to simply continue running until it hits a breakpoint, catches
3490 breakpoint
3503 takes place, set a breakpoint on `__raise_exception' (*note
3506 With a conditional breakpoint (*note Break Conditions: Conditions.)
3518 It is often necessary to eliminate a breakpoint, watchpoint, or
3520 to stop there. This is called "deleting" the breakpoint. A breakpoint
3526 their breakpoint numbers.
3528 It is not necessary to delete a breakpoint to proceed past it. GDB
3537 a breakpoint where your program just stopped.
3555 breakpoint ranges specified as arguments. If no argument is
3566 Rather than deleting a breakpoint, watchpoint, or catchpoint, you might
3567 prefer to "disable" it. This makes the breakpoint inoperative as if it
3568 had been deleted, but remembers the information on the breakpoint so
3573 breakpoint numbers as arguments. Use `info break' to print a list of
3577 Disabling and enabling a breakpoint that has multiple locations
3580 A breakpoint, watchpoint, or catchpoint can have any of four
3583 * Enabled. The breakpoint stops your program. A breakpoint set
3586 * Disabled. The breakpoint has no effect on your program.
3588 * Enabled once. The breakpoint stops your program, but then becomes
3591 * Enabled for deletion. The breakpoint stops your program, but
3593 breakpoint set with the `tbreak' command starts out in this state.
3600 listed. A disabled breakpoint has no effect but is not forgotten.
3602 remembered in case the breakpoint is enabled again later. You may
3619 Except for a breakpoint set with `tbreak' (*note Setting
3623 a breakpoint of its own, but it does not change the state of your other
3633 The simplest sort of breakpoint breaks every time your program reaches a
3634 specified place. You can also specify a "condition" for a breakpoint.
3636 (*note Expressions: Expressions.). A breakpoint with a condition
3644 condition `! ASSERT' on the appropriate breakpoint.
3656 there is another enabled breakpoint at the same address. (In that
3657 case, GDB might see the other breakpoint first and stop your program
3658 without checking the condition of this one.) Note that breakpoint
3660 for the purpose of performing side effects when a breakpoint is reached
3661 (*note Breakpoint Command Lists: Break Commands.).
3663 Break conditions can be specified when a breakpoint is set, by using
3673 Specify EXPRESSION as the break condition for breakpoint,
3675 breakpoint BNUM stops your program only if the value of EXPRESSION
3679 breakpoint. If EXPRESSION uses symbols not referenced in the
3680 context of the breakpoint, GDB prints an error message:
3685 `condition' command (or a command that sets a breakpoint with a
3690 Remove the condition from breakpoint number BNUM. It becomes an
3691 ordinary unconditional breakpoint.
3693 A special case of a breakpoint condition is to stop only when the
3694 breakpoint has been reached a certain number of times. This is so
3696 of the breakpoint. Every breakpoint has an ignore count, which is an
3698 no effect. But if your program reaches a breakpoint whose ignore count
3701 N, the breakpoint does not stop the next N times your program reaches
3705 Set the ignore count of breakpoint number BNUM to COUNT. The next
3706 COUNT times the breakpoint is reached, your program's execution
3710 To make the breakpoint stop the next time it is reached, specify a
3714 breakpoint, you can specify an ignore count directly as an
3718 If a breakpoint has a positive ignore count and a condition, the
3732 5.1.7 Breakpoint Command Lists
3735 You can give any breakpoint (or watchpoint or catchpoint) a series of
3736 commands to execute when your program stops due to that breakpoint. For
3747 To remove all commands from a breakpoint, type `commands' and
3750 With no argument, `commands' refers to the last breakpoint,
3751 watchpoint, or catchpoint set (not to the breakpoint most recently
3762 You can use breakpoint commands to start your program up again.
3769 breakpoint--which could have its own command list, leading to
3773 usual message about stopping at a breakpoint is not printed. This may
3776 see no sign that the breakpoint was reached. `silent' is meaningful
3777 only at the beginning of a breakpoint command list.
3783 For example, here is how you could use breakpoint commands to print
3793 One application for breakpoint commands is to compensate for one bug
3794 so you can test for another. Put a breakpoint just after the erroneous
3814 To save breakpoint definitions to a file use the `save breakpoints'
3818 This command saves all current breakpoint definitions together with
3822 To read the saved breakpoint definitions, use the `source' command
3826 valid anymore. Because the saved breakpoint definitions are
3829 the breakpoint definitions you're not interested in, or that can
3833 File: gdb.info, Node: Error in Breakpoints, Next: Breakpoint-related Warnings, Prev: Save Breakpoints, Up: Breakpoints
3852 File: gdb.info, Node: Breakpoint-related Warnings, Prev: Error in Breakpoints, Up: Breakpoints
3854 5.1.10 "Breakpoint address adjusted..."
3859 GDB will attempt to adjust the breakpoint's address to comply with the
3865 constrains the location of a breakpoint instruction within such a
3867 constraint by adjusting a breakpoint's address to the first in the
3872 a breakpoint's address will be adjusted from one source statement to
3874 breakpoint related behavior from what the user expects, a warning is
3875 printed when the breakpoint is first set and also when the breakpoint
3878 A warning like the one below is printed when setting a breakpoint
3881 warning: Breakpoint address adjusted from 0x00010414 to 0x00010410.
3885 a breakpoint set at the adjusted address will have the desired affect.
3886 If not, the breakpoint in question may be removed and other breakpoints
3888 sufficient to place the breakpoint at a later instruction. A
3889 conditional breakpoint may also be useful in some cases to prevent the
3890 breakpoint from triggering too often.
3895 warning: Breakpoint 1 address previously adjusted from 0x00010414
3899 action except in cases where the breakpoint is hit earlier or more
3913 program may stop even sooner, due to a breakpoint or a signal. (If it
3923 number of times to ignore a breakpoint at this location; its
3928 stopped due to a breakpoint. At other times, the argument to
3941 A typical technique for using stepping is to set a breakpoint (*note
3944 is believed to lie, run your program until it stops at that breakpoint,
3977 breakpoint is reached, or a signal not related to stepping occurs
4266 program stops (for example, at a breakpoint or while being stepped),
4306 thread runs into a breakpoint, a signal, or an exception before the
4309 Whenever GDB stops your program, due to a breakpoint or a signal, it
4310 automatically selects the thread where that breakpoint or signal
4328 hits a breakpoint during its timeslice, GDB does not change the
4343 want to resume them all until some breakpoint is hit. In the latter
4535 Use the qualifier `thread THREADNO' with a breakpoint command to
4537 particular thread reaches this breakpoint. THREADNO is one of the
4541 If you do not specify `thread THREADNO' when you set a breakpoint,
4542 the breakpoint applies to _all_ threads of your program.
4546 breakpoint condition, like this:
4558 multi-threaded programs. If one thread stops for a breakpoint, or for
4573 a breakpoint or for some other reason.
5452 printed; for the breakpoint commands, this is the line at which
5484 that contains ADDRESS. For `break' and other breakpoint oriented
6068 breakpoint at the overloaded symbol `String::after'. We choose three
6081 Breakpoint 1 at 0xb26c: file String.cc, line 867.
6082 Breakpoint 2 at 0xb344: file String.cc, line 875.
6083 Breakpoint 3 at 0xafcc: file String.cc, line 846.
6096 inserting a breakpoint on a function using an ambiguous name
6097 results in a breakpoint inserted on each possible match. However,
6445 address: `info breakpoints' (to the address of the last breakpoint
7287 `info breakpoint'. The type of `$_' is `void *' except when set
8177 breakpoint only on non-inlined copies of the function. This
8179 set a breakpoint by line number on the first line of the inlined
8184 incorrectly move the breakpoint to the next line of the enclosing
8186 future version of GDB; until then, set a breakpoint on an earlier
8347 Breakpoint 1 at 0x8048370: file sample.c, line 10.
8351 Breakpoint 1, main () at sample.c:10
8452 breakpoint (*note Set Breaks::), so you can manipulate it using
8453 standard breakpoint commands. For instance, as with breakpoints,
8464 Tracepoints do not support every breakpoint feature. Ignore counts
8695 Unlike breakpoint conditions, GDB does not actually evaluate the
8774 `actions' is actually equivalent to `commands' (*note Breakpoint
9652 breakpoint support has some limitations:
9658 unmapped overlays. However, if you set a breakpoint at the end of
9711 set a breakpoint there. If the overlay manager then calls this
9918 breakpoint), GDB sets the working language to the language recorded for
10512 `breakpoint menus'
10513 When you want a breakpoint in a function whose name is overloaded,
10514 GDB has the capability to display a menu of possible breakpoint
10661 example, to set a breakpoint at the `create' instance method of class
10684 As another example, to clear a breakpoint established at the
11779 Use the qualifier `task TASKNO' with a breakpoint command to
11781 particular Ada task reaches this breakpoint. TASKNO is one of the
11785 If you do not specify `task TASKNO' when you set a breakpoint, the
11786 breakpoint applies to _all_ tasks of your program.
11789 well; in this case, place `task TASKNO' before the breakpoint
11801 Breakpoint 5 at 0x120044cb0: file test_task_debug.adb, line 15.
11807 Breakpoint 5, test_task_debug () at test_task_debug.adb:15
12255 all. If we set a breakpoint on a function, that will cause GDB to
12259 Breakpoint 1 at 0x814e5da: file /home/gnu/src/gdb/dwarf2read.c,
12397 Execution stops again immediately if there is a breakpoint there.
12502 Breakpoint 1, func () at gdb.base/return-nodebug.c:29
12520 Breakpoint 2, 0x0040050b in func ()
13501 feel like debugging it, you can debug `gdb' with itself, breakpoint
14296 `set remote hardware-breakpoint-limit LIMIT'
14297 Restrict GDB to using LIMIT remote hardware breakpoint or
14382 `software-breakpoint'`Z0' `break'
14383 `hardware-breakpoint'`Z1' `hbreak'
14526 execution (for example, on a breakpoint), and mediates
14536 `breakpoint'
14538 breakpoint. Depending on the particular situation, this may be
14544 again, in that situation, you don't need to call `breakpoint' from
14548 Call `breakpoint' if none of these is true, or if you simply want
14584 is to just execute a breakpoint instruction (the "dirty" part is that
14649 breakpoint();
15104 start the program -- either by setting a breakpoint or letting the
15187 set the breakpoint at a raw memory address:
15190 Breakpoint 1 at 0x1e04eff0
15208 GDB. Mach exceptions, such as breakpoint traps, are not affected
15952 PMON monitor for breakpoint commands.
16097 breakpoints". A ranged breakpoint stops execution of the inferior
16099 specifies. To set a ranged breakpoint in GDB, use the `break-range'
16105 Set a breakpoint for an address range. START-LOCATION and
16110 breakpoint will stop execution of the inferior whenever it
16290 Breakpoint 1 at 0x12010000: file prog.c, line 3.
16293 Breakpoint 1, main (argc=1, argv=0xeffff21c) at prog.c:3
16350 breakpoint that suspends only after at least 5000 simulated clock ticks.
17354 Aside from breakpoint commands (*note Breakpoint Command Lists: Break
17482 execution stops in your program: before breakpoint commands are run,
18985 `gdb.BreakpointEvent' event indicates that a breakpoint has been
18988 -- Instance Variable of BreakpointEvent: breakpoint
18989 A reference to the breakpoint that was hit of type
18990 `gdb.Breakpoint'. *Note Breakpoints In Python::, for
18991 details of the `gdb.Breakpoint' object.
19942 Python code can manipulate breakpoints via the `gdb.Breakpoint' class.
19944 -- Method on Breakpoint: __init__ spec [type] [wp_class] [internal]
19945 Create a new breakpoint. SPEC is a string naming the location of
19946 the breakpoint, or an expression that defines a watchpoint. The
19949 TYPE denotes the breakpoint to create from the types defined later
19952 INTERNAL argument allows the breakpoint to become invisible to the
19953 user. The breakpoint will neither be reported when created, nor
19960 -- Operation on gdb.Breakpoint: stop (self)
19961 The `gdb.Breakpoint' class can be sub-classed and, in particular,
19963 defined as a sub-class of `gdb.Breakpoint', it will be called when
19964 the inferior reaches any location of a breakpoint which
19966 inferior will be stopped at the location of the breakpoint,
19978 class MyBreakpoint (gdb.Breakpoint):
19997 -- Method on Breakpoint: is_valid
19998 Return `True' if this `Breakpoint' object is valid, `False'
19999 otherwise. A `Breakpoint' object can become invalid if the user
20000 deletes the breakpoint. In this case, the object still exists,
20001 but the underlying breakpoint does not. In the cases of
20005 -- Method on Breakpoint: delete
20006 Permanently deletes the GDB breakpoint. This also invalidates the
20007 Python `Breakpoint' object. Any further access to this object's
20010 -- Instance Variable of Breakpoint: enabled
20011 This attribute is `True' if the breakpoint is enabled, and `False'
20014 -- Instance Variable of Breakpoint: silent
20015 This attribute is `True' if the breakpoint is silent, and `False'
20018 Note that a breakpoint can also be silent if it has commands and
20022 -- Instance Variable of Breakpoint: thread
20023 If the breakpoint is thread-specific, this attribute holds the
20024 thread id. If the breakpoint is not thread-specific, this
20027 -- Instance Variable of Breakpoint: task
20028 If the breakpoint is Ada task-specific, this attribute holds the
20029 Ada task id. If the breakpoint is not task-specific (or the
20033 -- Instance Variable of Breakpoint: ignore_count
20034 This attribute holds the ignore count for the breakpoint, an
20037 -- Instance Variable of Breakpoint: number
20038 This attribute holds the breakpoint's number -- the identifier
20039 used by the user to manipulate the breakpoint. This attribute is
20042 -- Instance Variable of Breakpoint: type
20043 This attribute holds the breakpoint's type -- the identifier used
20044 to determine the actual breakpoint type or use-case. This
20047 -- Instance Variable of Breakpoint: visible
20048 This attribute tells whether the breakpoint is visible to the user
20056 Normal code breakpoint.
20059 Watchpoint breakpoint.
20070 -- Instance Variable of Breakpoint: hit_count
20071 This attribute holds the hit count for the breakpoint, an integer.
20075 -- Instance Variable of Breakpoint: location
20076 This attribute holds the location of the breakpoint, as specified
20077 by the user. It is a string. If the breakpoint does not have a
20081 -- Instance Variable of Breakpoint: expression
20082 This attribute holds a breakpoint expression, as specified by the
20083 user. It is a string. If the breakpoint does not have an
20084 expression (the breakpoint is not a watchpoint) the attribute's
20087 -- Instance Variable of Breakpoint: condition
20088 This attribute holds the condition of the breakpoint, as specified
20092 -- Instance Variable of Breakpoint: commands
20093 This attribute holds the commands attached to the breakpoint. If
20495 the breakpoint type:
20498 Breakpoint which was hit at least once.
20501 Breakpoint which was never hit.
20504 Hardware breakpoint which was hit at least once.
20507 Hardware breakpoint which was never hit.
20509 The second marker indicates whether the breakpoint is enabled or not:
20512 Breakpoint is enabled.
20515 Breakpoint is disabled.
20919 tells GDB to set a breakpoint on the source line point is on.
20993 * GDB/MI Breakpoint Commands::
21091 current thread be changed. For example, when stopping on a breakpoint
21092 it is reasonable to switch to the thread where breakpoint is hit. For
21142 `set', and breakpoint commands, still access the target in the context
21368 client should handle (e.g., a new breakpoint information). All
21396 query the user will behave as if the user replied yes, breakpoint
21528 of GDB/MI commands (e.g., a breakpoint modified) or a result of target
21548 `breakpoint-hit'
21549 A breakpoint was reached.
21587 for example by hitting a breakpoint. Depending on whether all-stop
21752 Setting a Breakpoint
21755 Setting a breakpoint generates synchronous output which contains
21756 detailed information of the breakpoint.
21759 <- ^done,bkpt={number="1",type="breakpoint",disp="keep",
21773 <- *stopped,reason="breakpoint-hit",disp="keep",bkptno="1",thread-id="0",
21810 File: gdb.info, Node: GDB/MI Command Description Format, Next: GDB/MI Breakpoint Commands, Prev: GDB/MI Simple Examples, Up: GDB/MI
21854 File: gdb.info, Node: GDB/MI Breakpoint Commands, Next: GDB/MI Program Context, Prev: GDB/MI Command Description Format, Up: GDB/MI
21856 27.8 GDB/MI Breakpoint Commands
21869 The breakpoint number NUMBER is not in effect until it has been hit
21884 ^done,bkpt={number="1",type="breakpoint",disp="keep",
21900 body=[bkpt={number="1",type="breakpoint",disp="keep",enabled="y",
21913 Specifies the CLI commands that should be executed when breakpoint
21918 breakpoint is hit and then continuing.
21930 ^done,bkpt={number="1",type="breakpoint",disp="keep",
21946 Breakpoint NUMBER will stop the program only if the condition in
21970 body=[bkpt={number="1",type="breakpoint",disp="keep",enabled="y",
21981 -break-delete ( BREAKPOINT )+
21983 Delete the breakpoint(s) whose number(s) are specified in the
21984 argument list. This is obviously reflected in the breakpoint list.
22015 -break-disable ( BREAKPOINT )+
22017 Disable the named BREAKPOINT(s). The field `enabled' in the break
22018 list is now set to `n' for the named BREAKPOINT(s).
22040 body=[bkpt={number="2",type="breakpoint",disp="keep",enabled="n",
22051 -break-enable ( BREAKPOINT )+
22053 Enable (previously disabled) BREAKPOINT(s).
22075 body=[bkpt={number="2",type="breakpoint",disp="keep",enabled="y",
22086 -break-info BREAKPOINT
22088 Get information about a single breakpoint.
22093 The corresponding GDB command is `info break BREAKPOINT'.
22123 Insert a temporary breakpoint.
22126 Insert a hardware breakpoint.
22129 Make the breakpoint conditional on CONDITION.
22136 files or functions), create a pending breakpoint. Without this
22137 flag, GDB will report an error, and won't create a breakpoint, if
22141 Create a disabled breakpoint.
22157 where NUMBER is the GDB number for this breakpoint, FUNCNAME is the
22158 name of the function where the breakpoint was inserted, FILENAME is the
22161 the breakpoint has been hit (always 0 for -break-insert but may be
22192 body=[bkpt={number="1",type="breakpoint",disp="keep",enabled="y",
22195 bkpt={number="2",type="breakpoint",disp="del",enabled="y",
22217 number of the breakpoint
22220 type of the breakpoint: `breakpoint' or `watchpoint'
22223 should the breakpoint be deleted or disabled when it is hit: `keep'
22227 is the breakpoint enabled or no: `y' or `n'
22230 memory location at which the breakpoint is set
22233 logical location of the breakpoint, expressed by function name,
22237 number of times the breakpoint has been hit
22259 body=[bkpt={number="1",type="breakpoint",disp="keep",enabled="y",
22261 bkpt={number="2",type="breakpoint",disp="keep",enabled="y",
22289 the breakpoint referred to by TRACEPOINT-NUMBER is not a tracepoint,
22378 body=[bkpt={number="1",type="breakpoint",disp="keep",enabled="y",
22402 body=[bkpt={number="1",type="breakpoint",disp="keep",enabled="y",
22425 body=[bkpt={number="1",type="breakpoint",disp="keep",enabled="y",
22433 File: gdb.info, Node: GDB/MI Program Context, Next: GDB/MI Thread Commands, Prev: GDB/MI Breakpoint Commands, Up: GDB/MI
22797 *stopped,reason="breakpoint-hit",disp="keep",bkptno="2",frame={
23013 000*stopped,reason="breakpoint-hit",disp="keep",bkptno="1",
23038 executes until either a breakpoint is encountered or the program exits.
23062 *stopped,reason="breakpoint-hit",disp="keep",bkptno="1",
24472 *stopped,reason="breakpoint-hit",disp="keep",bkptno="1",frame={
25896 ~"Breakpoint 1 at 0x8074fc6: file ../../src/gdb/main.c, line 743.\n"
25975 ^done,bkpt={number="1",type="breakpoint",disp="keep",enabled="y",
25986 *stopped,reason="breakpoint-hit",disp="keep",bkptno="1",thread-id="0",
26190 added or deleted a breakpoint.
26240 The program hit breakpoint number NUMBER.
26294 variable to find existing code, and puts a breakpoint in the function
26337 /* GDB puts a breakpoint in this function. */
26371 When GDB is attached and the breakpoint fires, GDB uses the
28545 breakpoint numbers. The type column identifies what kind of
28546 breakpoint is shown:
28548 `breakpoint'
28549 Normal, explicitly set breakpoint.
28555 Internal breakpoint, used to handle correctly stepping through
28559 Internal breakpoint at the target of a `longjmp'.
28562 Temporary internal breakpoint used by the GDB `until' command.
28565 Temporary internal breakpoint used by the GDB `finish'
28578 originally at the breakpoint location. It is also known as
28680 Breakpoint 2, add (a=2, b=3) at ...
28828 hardware breakpoint or watchpoint, and when the inferior triggers
28829 a hardware-assisted breakpoint or watchpoint.
29102 Set (MODE is `S') or clear (MODE is `C') a breakpoint at ADDR.
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
29540 Insert (`Z0') or remove (`z0') a memory breakpoint at address ADDR
29543 A memory breakpoint is implemented by replacing the instruction at
29544 ADDR with a software breakpoint or trap instruction. The KIND is
29545 target-specific and typically indicates the size of the breakpoint
29547 insert either a 2 or 4 byte breakpoint. Some architectures have
29568 Insert (`Z1') or remove (`z1') a hardware breakpoint at address
29571 A hardware breakpoint is implemented using a mechanism that is not
29575 _Implementation note: A hardware breakpoint is not affected by code
29660 latency. Single-step and breakpoint traps are reported this way.
30623 E.5.1.1 Breakpoint Kinds
30626 These breakpoint kinds are defined for the `Z0' and `Z1' packets.
30629 16-bit Thumb mode breakpoint.
30632 32-bit Thumb mode (Thumb-2) breakpoint.
30635 32-bit ARM mode breakpoint.
31264 breakpoint, or a fault, only the affected thread is stopped; any other
31445 <- target hits breakpoint and sends a Txx packet
35285 * -break-after: GDB/MI Breakpoint Commands.
35287 * -break-commands: GDB/MI Breakpoint Commands.
35289 * -break-condition: GDB/MI Breakpoint Commands.
35291 * -break-delete: GDB/MI Breakpoint Commands.
35293 * -break-disable: GDB/MI Breakpoint Commands.
35295 * -break-enable: GDB/MI Breakpoint Commands.
35297 * -break-info: GDB/MI Breakpoint Commands.
35299 * -break-insert: GDB/MI Breakpoint Commands.
35301 * -break-list: GDB/MI Breakpoint Commands.
35303 * -break-passcount: GDB/MI Breakpoint Commands.
35305 * -break-watch: GDB/MI Breakpoint Commands.
35533 * __init__ on Breakpoint: Breakpoints In Python.
35696 * breakpoint: Events In Python. (line 102)
35697 * breakpoint address adjusted: Breakpoint-related Warnings.
35699 * breakpoint annotation: Annotations for Running.
35701 * breakpoint commands: Break Commands. (line 6)
35702 * breakpoint commands for GDB/MI: GDB/MI Breakpoint Commands.
35704 * breakpoint conditions: Conditions. (line 6)
35705 * breakpoint numbers: Breakpoints. (line 41)
35706 * breakpoint on events: Breakpoints. (line 33)
35707 * breakpoint on memory address: Breakpoints. (line 20)
35708 * breakpoint on variable modification: Breakpoints. (line 20)
35709 * breakpoint ranges: Breakpoints. (line 48)
35710 * breakpoint subroutine, remote: Stub Contents. (line 31)
35999 * delete on Breakpoint: Breakpoints In Python.
36137 * enable/disable a breakpoint: Disabling. (line 6)
36143 * end (breakpoint commands): Break Commands. (line 11)
36328 * gdb.Breakpoint: Breakpoints In Python.
36482 * GDB/MI, breakpoint commands: GDB/MI Breakpoint Commands.
36583 * ignore count (of breakpoint): Conditions. (line 66)
36745 * is_valid on Breakpoint: Breakpoints In Python.
36796 * latest breakpoint: Set Breaks. (line 6)
37062 * negative breakpoint numbers: Set Breaks. (line 333)
37083 * non-member C++ functions, set breakpoint in: Set Breaks. (line 108)
37085 * non-stop mode, and breakpoint always-inserted: Set Breaks. (line 326)
37428 * ranged breakpoint: PowerPC Embedded. (line 30)
37657 * set breakpoint always-inserted: Set Breaks. (line 314)
37658 * set breakpoint auto-hw: Set Breaks. (line 294)
37659 * set breakpoint pending: Set Breaks. (line 263)
37873 * show breakpoint always-inserted: Set Breaks. (line 314)
37874 * show breakpoint auto-hw: Set Breaks. (line 294)
37875 * show breakpoint pending: Set Breaks. (line 263)
38127 * stop on gdb.Breakpoint: Breakpoints In Python.
38626 Node: Breakpoint-related Warnings163227
38793 Ref: set remote hardware-breakpoint-limit587214
38917 Node: GDB/MI Breakpoint Commands873425
39006 Ref: insert breakpoint or watchpoint packet1129080
