Re: Multiple breakpoint locations

[Vladimir Prus <ghost at cs dot msu dot su>]

Eli Zaretskii wrote:

>> From: Nick Roberts <nickrob@snap.net.nz>
>> Date: Wed, 14 Nov 2007 08:15:27 +1300
>> 
>> 
>> The new code for breakpoints with multiple locations looks very good and
>> addresses a common complaint about GDB.  I have a couple of points and
>> apologise if they have already been discussed.
> 
> 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.
> 
> 
> Index: gdb/doc/gdb.texinfo
> ===================================================================
> RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
> retrieving revision 1.444
> diff -u -r1.444 gdb.texinfo
> --- gdb/doc/gdb.texinfo       15 Nov 2007 18:43:23 -0000      1.444
> +++ gdb/doc/gdb.texinfo       17 Nov 2007 11:48:53 -0000
> @@ -2992,7 +2992,7 @@
>  @item Enabled or Disabled
>  Enabled breakpoints are marked with @samp{y}.  @samp{n} marks breakpoints
>  that are not enabled.  An optional @samp{(p)} suffix marks pending
> -breakpoints --- breakpoints for which address is either not yet
> +breakpoints---breakpoints for which address is either not yet
>  resolved, pending load of a shared library, or for which address was
>  in a shared library that was since unloaded.  Such breakpoint won't
>  fire until a shared library that has the symbol or line referred by
> @@ -3001,7 +3001,7 @@
>  Where the breakpoint is in your program, as a memory address.  For a
>  pending breakpoint whose address is not yet known,  this field will
>  contain @samp{<PENDING>}.  A breakpoint with several locations will
> -have @samp{<MULTIPLE>} in this field --- see below for details.
> +have @samp{<MULTIPLE>} in this field---see below for details.
>  @item What
>  Where the breakpoint is in the source for your program, as a file and
>  line number.  For a pending breakpoint, the original string passed to
> @@ -3060,16 +3060,16 @@
>  In all those cases, @value{GDBN} will insert a breakpoint at all
>  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 say what functions those locations are in.  The number
> -column for a location has number in the format
> +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:
> +
>  @smallexample
>  Num     Type           Disp Enb  Address    What
>  1       breakpoint     keep y    <MULTIPLE>
> @@ -3081,11 +3081,17 @@
>  
>  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.
> +@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 be long to their parent breakpoint (with

Was "be long" meant to be "belong"?

- Volodya