* gdbint.texinfo (Native Conditionals): Remove PREPARE_TO_PROCEED.

diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog
index 0edd33b8e4aa1a7c9573267005e8d7586d9b9e48..9f58e203176159154a72fff2f5455290d7c70906 100644 (file)
--- a/gdb/doc/ChangeLog
+++ b/gdb/doc/ChangeLog
@@ -1,3 +1,7 @@
+2003-06-19  Daniel Jacobowitz  <drow@mvista.com>
+
+       * gdbint.texinfo (Native Conditionals): Remove PREPARE_TO_PROCEED.
+
 2003-06-18  Daniel Jacobowitz  <drow@mvista.com>
 
         * gdb.texinfo (Remote Debugging): New section "Connecting to a

diff --git a/gdb/doc/gdbint.texinfo b/gdb/doc/gdbint.texinfo
index 68ff5dc265b97171822150764ea83d35a3313ed4..76521dbe48a642af7d6c9c4da395e218d0083375 100644 (file)
--- a/gdb/doc/gdbint.texinfo
+++ b/gdb/doc/gdbint.texinfo
@@ -4494,23 +4494,6 @@ root directory.
 Define this to be able to, when a breakpoint insertion fails, warn the
 user that another process may be running with the same executable.
 
-@item PREPARE_TO_PROCEED (@var{select_it})
-@findex PREPARE_TO_PROCEED
-This (ugly) macro allows a native configuration to customize the way the
-@code{proceed} function in @file{infrun.c} deals with switching between
-threads.
-
-In a multi-threaded task we may select another thread and then continue
-or step.  But if the old thread was stopped at a breakpoint, it will
-immediately cause another breakpoint stop without any execution (i.e. it
-will report a breakpoint hit incorrectly).  So @value{GDBN} must step over it
-first.
-
-If defined, @code{PREPARE_TO_PROCEED} should check the current thread
-against the thread that reported the most recent event.  If a step-over
-is required, it returns TRUE.  If @var{select_it} is non-zero, it should
-reselect the old thread.
-
 @item PROC_NAME_FMT
 @findex PROC_NAME_FMT
 Defines the format for the name of a @file{/proc} device.  Should be