From 4ca61388162d64779d560c00e7bef17a29c9fb4b Mon Sep 17 00:00:00 2001 From: Daniel Jacobowitz Date: Thu, 19 Jun 2003 15:04:05 +0000 Subject: [PATCH] * gdbint.texinfo (Native Conditionals): Remove PREPARE_TO_PROCEED. --- gdb/doc/ChangeLog | 4 ++++ gdb/doc/gdbint.texinfo | 17 ----------------- 2 files changed, 4 insertions(+), 17 deletions(-) diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog index 0edd33b8e4..9f58e20317 100644 --- a/gdb/doc/ChangeLog +++ b/gdb/doc/ChangeLog @@ -1,3 +1,7 @@ +2003-06-19 Daniel Jacobowitz + + * gdbint.texinfo (Native Conditionals): Remove PREPARE_TO_PROCEED. + 2003-06-18 Daniel Jacobowitz * gdb.texinfo (Remote Debugging): New section "Connecting to a diff --git a/gdb/doc/gdbint.texinfo b/gdb/doc/gdbint.texinfo index 68ff5dc265..76521dbe48 100644 --- 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 -- 2.34.1