Debugging with GDB (September 2007)

276 Debugging with GDB
^done,bkpt=number="2",type="breakpoint",disp="keep",enabled="y",addr="0x00010774",
file="recursive2.c",line="11",times="0"(gdb)
-break-list
^done,BreakpointTable={nr_rows="2",nr_cols="6",
hdr=[{width="3",alignment="-1",col_name="number",colhdr="Num"},
{width="14",alignment="-1",col_name="type",colhdr="Type"},
{width="4",alignment="-1",col_name="disp",colhdr="Disp"},
{width="3",alignment="-1",col_name="enabled",colhdr="Enb"},
{width="10",alignment="-1",col_name="addr",colhdr="Address"},
{width="40",alignment="2",col_name="what",colhdr="What"}],
body=[bkpt={number="1",type="breakpoint",disp="keep",enabled="y",
addr="0x0001072c", func="main",file="recursive2.c",line="4",times="0"},
bkpt={number="2",type="breakpoint",disp="del",enabled="y",
addr="0x00010774",func="foo",file="recursive2.c",line="11",times="0"}]}
(gdb)
-break-insert -r foo.*
~int foo(int, int);
^done,bkpt={number="3",addr="0x00010774",file="recursive2.c",line="11"}
(gdb)
The -break-list com mand
Synopsis
-break-list
Displays the list of inserted breakp oints, showing the following fields:
‘Number’ number of the breakpoint
‘Type’ type of the breakpoint: ‘breakpoint’ or ‘watchpoint’
‘Disposition’
should the breakp oint be deleted or disabled when it is hit: ‘keep’ or ‘nokeep’
‘Enabled’ is the breakpoint enabled or no: ‘y’ or ‘n’
‘Address’ memory location at which the breakpoint is set
‘What’ logical location of the breakpoint, expressed by function name, file name, line
numb e r
‘Times’ numb er of times the breakpoint has been hit
If there are no breakpoints or watchpoints, the BreakpointTable body field is an empty
list.
GDB command
The corresponding GDB command is ‘info break’.
Example
(gdb)
-break-list