2004-02-26 Jeff Johnston <jjohnstn@redhat.com>

        * gdb.texinfo (breakpoints): Add information about the
        new "set breakpoint pending" and "show breakpoint pending"
        commands.

diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog
index e08d7d920833aa9b0734d1d4ac2ca493235c2ce7..47f6e7c0e55d100559f6e542c14128e964196cc9 100644 (file)
--- a/gdb/doc/ChangeLog
+++ b/gdb/doc/ChangeLog
@@ -1,3 +1,9 @@
+2004-02-26  Jeff Johnston  <jjohnstn@redhat.com>
+
+       * gdb.texinfo (breakpoints): Add information about the
+       new "set breakpoint pending" and "show breakpoint pending"
+       commands.
+
 2004-02-26  Andrew Cagney  <cagney@redhat.com>
 
        * gdbint.texinfo (Coding): Document use of gdbarch_obstack_zalloc

diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index d3a8c523c148f3672dc9be1c1205c41201bd3867..06b4aa12cc45906ad06218b3918e413689e8a367 100644 (file)
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -2639,15 +2639,42 @@ the breakpoints are conditional, this is even useful
 (@pxref{Conditions, ,Break conditions}).
 
 @cindex pending breakpoints
-If a specified breakpoint location cannot be found, @value{GDBN} will
-prompt you
-as to whether to make the breakpoint pending on a future shared
-library load.  This is useful for setting breakpoints at the start of your
+If a specified breakpoint location cannot be found, it may be due to the fact
+that the location is in a shared library that is yet to be loaded.  In such
+a case, you may want @value{GDBN} to create a special breakpoint (known as
+a @dfn{pending breakpoint}) that
+attempts to resolve itself in the future when an appropriate shared library
+gets loaded.
+
+Pending breakpoints are useful to set at the start of your
 @value{GDBN} session for locations that you know will be dynamically loaded
 later by the program being debugged.  When shared libraries are loaded,
-a check is made to see if the load resoloves any pending breakpoint locations.
-If a pending breakpoint location has been resolved,
-a real breakpoint is created and the original pending breakpoint is removed.
+a check is made to see if the load resolves any pending breakpoint locations.
+If a pending breakpoint location gets resolved,
+a regular breakpoint is created and the original pending breakpoint is removed.
+
+@value{GDBN} provides some additional commands for controlling pending
+breakpoint support:
+
+@kindex set breakpoint pending
+@kindex show breakpoint pending
+@table @code
+@item set breakpoint pending auto
+This is the default behavior.  When @value{GDBN} cannot find the breakpoint
+location, it queries you whether a pending breakpoint should be created.
+
+@item set breakpoint pending on
+This indicates that an unrecognized breakpoint location should automatically
+result in a pending breakpoint being created.
+
+@item set breakpoint pending off
+This indicates that pending breakpoints are not to be created.  Any
+unrecognized breakpoint location results in an error.  This setting does
+not affect any pending breakpoints previously created.
+
+@item show breakpoint pending
+Show the current behavior setting for creating pending breakpoints.
+@end table
 
 @cindex operations allowed on pending breakpoints
 Normal breakpoint operations apply to pending breakpoints as well.  You may