diff options
| author | Eli Zaretskii <eliz@gnu.org> | 2007-09-28 11:09:55 +0000 |
|---|---|---|
| committer | Eli Zaretskii <eliz@gnu.org> | 2007-09-28 11:09:55 +0000 |
| commit | fcda367bb90421d3d1ff981d70f534f70c8b12f2 (patch) | |
| tree | f144d958249ac45b43da06085cf3c991be48c210 /gdb | |
| parent | 5582a088529adbefbcf65cfa3e6f47fa087153a2 (diff) | |
| download | gdb-fcda367bb90421d3d1ff981d70f534f70c8b12f2.zip gdb-fcda367bb90421d3d1ff981d70f534f70c8b12f2.tar.gz gdb-fcda367bb90421d3d1ff981d70f534f70c8b12f2.tar.bz2 | |
(Set Breaks): Fix a typo.
Diffstat (limited to 'gdb')
| -rw-r--r-- | gdb/doc/gdb.texinfo | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo index 9b9d16e..3c4d99d 100644 --- a/gdb/doc/gdb.texinfo +++ b/gdb/doc/gdb.texinfo @@ -3038,7 +3038,7 @@ your program. There is nothing silly or meaningless about this. When the breakpoints are conditional, this is even useful (@pxref{Conditions, ,Break Conditions}). -It is possible that a breakpoint correspond to several locations +It is possible that a breakpoint corresponds to several locations in your program. Examples of this situation are: @itemize @bullet @@ -3066,7 +3066,7 @@ 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 +column for a location has number in the format @var{breakpoint-number}.@var{location-number}. For example: @@ -3089,11 +3089,11 @@ The shared library may 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 -set a breakpoint in a shared library at the beginning of your +set a breakpoint in a shared library at the beginning of your debugging session, when the library is not loaded, and when the symbols from the library are not available. When you try to set breakpoint, @value{GDBN} will ask you if you want to set -a so called @dfn{pending breakpoint} --- breakpoint whose address +a so called @dfn{pending breakpoint} --- breakpoint whose address is not yet resolved. After the program is run, whenever a new shared library is loaded, @@ -3146,7 +3146,7 @@ software breakpoints should be used, depending on whether the breakpoint address is read-only or read-write. This applies to breakpoints set with the @code{break} command as well as to internal breakpoints set by commands like @code{next} and @code{finish}. For -breakpoints set with @code{hbreak}, @value{GDBN} will always use hardware +breakpoints set with @code{hbreak}, @value{GDBN} will always use hardware breakpoints. You can control this automatic behaviour with the following commands:: |