diff options
Diffstat (limited to 'gdb/doc')
| -rw-r--r-- | gdb/doc/ChangeLog | 7 | ||||
| -rw-r--r-- | gdb/doc/gdb.texinfo | 35 | ||||
| -rw-r--r-- | gdb/doc/gdbint.texinfo | 5 |
3 files changed, 9 insertions, 38 deletions
diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog index 7283ad4..d17ad23 100644 --- a/gdb/doc/ChangeLog +++ b/gdb/doc/ChangeLog @@ -1,3 +1,10 @@ +2009-01-07 Pedro Alves <pedro@codesourcery.com> + + * gdb.texinfo (Error in Breakpoints): Delete mention of "The same + program may be running in another process" errors. + * gdbint.texinfo (Native Conditionals): Delete + ONE_PROCESS_WRITETEXT description. + 2009-01-07 Joel Brobecker <brobecker@adacore.com> * gdbint.texinfo (Start of New Year Procedure): Add the "coding" diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo index f6b7a1c..d85721a 100644 --- a/gdb/doc/gdb.texinfo +++ b/gdb/doc/gdb.texinfo @@ -4035,40 +4035,9 @@ end @c @ifclear BARETARGET @node Error in Breakpoints @subsection ``Cannot insert breakpoints'' -@c -@c FIXME!! 14/6/95 Is there a real example of this? Let's use it. -@c -Under some operating systems, breakpoints cannot be used in a program if -any other process is running that program. In this situation, -attempting to run or continue a program with a breakpoint causes -@value{GDBN} to print an error message: - -@smallexample -Cannot insert breakpoints. -The same program may be running in another process. -@end smallexample - -When this happens, you have three ways to proceed: - -@enumerate -@item -Remove or disable the breakpoints, then continue. - -@item -Suspend @value{GDBN}, and copy the file containing your program to a new -name. Resume @value{GDBN} and use the @code{exec-file} command to specify -that @value{GDBN} should run your program under that name. -Then start your program again. - -@item -Relink your program so that the text segment is nonsharable, using the -linker option @samp{-N}. The operating system limitation may not apply -to nonsharable executables. -@end enumerate -@c @end ifclear -A similar message can be printed if you request too many active -hardware-assisted breakpoints and watchpoints: +If you request too many active hardware-assisted breakpoints and +watchpoints, you will see this error message: @c FIXME: the precise wording of this message may change; the relevant @c source change is not committed yet (Sep 3, 1999). diff --git a/gdb/doc/gdbint.texinfo b/gdb/doc/gdbint.texinfo index adc8ca8..6a9ea6c 100644 --- a/gdb/doc/gdbint.texinfo +++ b/gdb/doc/gdbint.texinfo @@ -4525,11 +4525,6 @@ undefined) in @file{nm-@var{system}.h}. An x86-based machine can define this to use the generic x86 watchpoint support; see @ref{Algorithms, I386_USE_GENERIC_WATCHPOINTS}. -@item ONE_PROCESS_WRITETEXT -@findex ONE_PROCESS_WRITETEXT -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 PROC_NAME_FMT @findex PROC_NAME_FMT Defines the format for the name of a @file{/proc} device. Should be |