This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: Multiple breakpoint locations
- From: Nick Roberts <nickrob at snap dot net dot nz>
- To: Eli Zaretskii <eliz at gnu dot org>
- Cc: gdb-patches at sources dot redhat dot com
- Date: Sun, 18 Nov 2007 14:24:41 +1300
- Subject: Re: Multiple breakpoint locations
- References: <18233.63439.953202.586908@kahikatea.snap.net.nz> <ubq9tccj5.fsf@gnu.org>
> Thanks for your suggestions, I fixed the manual as shown below:
>
> 2007-11-17 Eli Zaretskii <eliz@gnu.org>
>
> * gdb.texinfo (Set Breaks, Disabling): Clarify behavior of
> breakpoints with multiple locations.
> (Breakpoint Menus): Improve wording.
Since the concept of a parent breakpoint has been used, perhaps this could
be used with "header row". Also breakpoint-number is abbreviated to BNUM
elsewhere. Here are a few ideas:
--
Nick http://www.inet.net.nz/~nickrob
*** gdb.texinfo.~1.446.~ 2007-11-18 13:23:21.000000000 +1300
--- gdb.texinfo 2007-11-18 14:19:45.000000000 +1300
*************** In all those cases, @value{GDBN} will in
*** 3061,3072 ****
the relevant locations.
A breakpoint with multiple locations is displayed in the breakpoint
! table using several rows---one header row, followed by one row for
! each breakpoint location. The header row has @samp{<MULTIPLE>} in the
! address column. The rows for individual locations contain the actual
! addresses for locations, and show the functions to which those
! locations belong. The number column for a location is of the form
! @var{breakpoint-number}.@var{location-number}.
For example:
--- 3061,3074 ----
the relevant locations.
A breakpoint with multiple locations is displayed in the breakpoint
! table using several rows---one header row for the parent breakpoint,
! followed by one row for each breakpoint location. The header row has
! @samp{<MULTIPLE>} in the address column. The rows for individual
! locations contain the actual addresses for locations, and show the
! functions to which those locations belong. The number column for a
! location is of the form @var{bnum}.@var{lnum} where @var{bnum} is is
! the number of the parent breakpoint and @var{lnum} the location
! number.
For example:
*************** Num Type Disp Enb Address
*** 3080,3093 ****
@end smallexample
Each location can be individually enabled or disabled by passing
! @var{breakpoint-number}.@var{location-number} as argument to the
! @code{enable} and @code{disable} commands. Note that you cannot
! delete the individual locations from the list, you can only delete the
! entire list of locations that belong to their parent breakpoint (with
! the @kbd{delete @var{num}} command, where @var{num} is the number of
! the parent breakpoint, 1 in the above example). Disabling or enabling
! the parent breakpoint (@pxref{Disabling}) affects all of the locations
! that belong to that breakpoint.
@cindex pending breakpoints
It's quite common to have a breakpoint inside a shared library.
--- 3082,3094 ----
@end smallexample
Each location can be individually enabled or disabled by passing
! @var{bnum}.@var{lnum} as argument to the @code{enable} and
! @code{disable} commands. Note that you cannot delete the individual
! locations from the list, you can only delete the entire list of
! locations that belong to their parent breakpoint (with the @kbd{delete
! @var{bnum}} command, where @var{bnum} is 1 in the above example).
! Disabling or enabling the parent breakpoint (@pxref{Disabling})
! affects all of the locations that belong to that breakpoint.
@cindex pending breakpoints
It's quite common to have a breakpoint inside a shared library.