* gdb.texinfo (Set Breaks, Disabling): Clarify behavior of
breakpoints with multiple locations. (Breakpoint Menus): Improve wording. (Output): Fix last change.
This commit is contained in:
parent
dd8670e56c
commit
3b784c4f87
|
@ -1,3 +1,10 @@
|
|||
2007-11-17 Eli Zaretskii <eliz@gnu.org>
|
||||
|
||||
* gdb.texinfo (Set Breaks, Disabling): Clarify behavior of
|
||||
breakpoints with multiple locations.
|
||||
(Breakpoint Menus): Improve wording.
|
||||
(Output): Fix last change.
|
||||
|
||||
2007-11-17 Ulrich Weigand <uweigand@de.ibm.com>
|
||||
|
||||
* Makefile.in (Makefile): Do not depend on target_makefile_frag.
|
||||
|
@ -18,7 +25,7 @@
|
|||
|
||||
2007-11-05 Luis Machado <luisgpm@br.ibm.com>
|
||||
|
||||
* gdb.texinfo: Update printf command's description.
|
||||
* gdb.texinfo (Output): Update printf command's description.
|
||||
|
||||
2007-10-30 Daniel Jacobowitz <dan@codesourcery.com>
|
||||
|
||||
|
|
|
@ -3060,16 +3060,16 @@ several places where that function is inlined.
|
|||
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 @@ Num Type Disp Enb Address What
|
|||
|
||||
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
|
||||
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.
|
||||
The shared library may be loaded and unloaded explicitly,
|
||||
Shared libraries can be loaded and unloaded explicitly,
|
||||
and possibly repeatedly, as the program is executed. To support
|
||||
this use case, @value{GDBN} updates breakpoint locations whenever
|
||||
any shared library is loaded or unloaded. Typically, you would
|
||||
|
@ -3544,6 +3550,9 @@ or more breakpoint numbers as arguments. Use @code{info break} or
|
|||
@code{info watch} to print a list of breakpoints, watchpoints, and
|
||||
catchpoints if you do not know which numbers to use.
|
||||
|
||||
Disabling and enabling a breakpoint that has multiple locations
|
||||
affects all of its locations.
|
||||
|
||||
A breakpoint, watchpoint, or catchpoint can have any of four different
|
||||
states of enablement:
|
||||
|
||||
|
@ -3808,8 +3817,8 @@ single function name
|
|||
to be defined several times, for application in different contexts.
|
||||
This is called @dfn{overloading}. When a function name is overloaded,
|
||||
@samp{break @var{function}} is not enough to tell @value{GDBN} where you want
|
||||
a breakpoint. If you realize this is a problem, you can use
|
||||
something like @samp{break @var{function}(@var{types})} to specify which
|
||||
a breakpoint. You can use explicit signature of the function, as in
|
||||
@samp{break @var{function}(@var{types})}, to specify which
|
||||
particular version of the function you want. Otherwise, @value{GDBN} offers
|
||||
you a menu of numbered choices for different possible breakpoints, and
|
||||
waits for your selection with the prompt @samp{>}. The first two
|
||||
|
@ -16621,7 +16630,7 @@ letters:
|
|||
|
||||
If the underlying @code{C} implementation used to build @value{GDBN} has
|
||||
support for the three conversion letters for DFP types, other modifiers
|
||||
such as width and precision will also be available for @value{GDB} to use.
|
||||
such as width and precision will also be available for @value{GDBN} to use.
|
||||
|
||||
In case there is no such @code{C} support, no additional modifiers will be
|
||||
available and the value will be printed in the standard way.
|
||||
|
|
Loading…
Reference in New Issue