2011-10-07 Phil Muldoon <pmuldoon@redhat.com>

	PR python/12930
	PR python/12802

	* gdb.texinfo (Breakpoints In Python): Clarify behavior in the
	stop method.

diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog
index 398f3472148fb84da6f20e336f944ead3efaabb0..a59fa34f84da0ddb5b753e0309aa287d1b94ff86 100644 (file)
--- a/gdb/doc/ChangeLog
+++ b/gdb/doc/ChangeLog
@@ -1,3 +1,11 @@
+2011-10-07  Phil Muldoon  <pmuldoon@redhat.com>
+
+       PR python/12930
+       PR python/12802
+
+       * gdb.texinfo (Breakpoints In Python): Clarify behavior in the
+       stop method.
+
 2011-10-07  Ulrich Weigand  <ulrich.weigand@linaro.org>
 
        * gdb.texinfo (Starting your Program): "set disable-randomization"

diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index 26f6216eb86b9ab4968585de302e7d3a32d98c02..bb6e43c44147fdd6ba0e7665b7ff172737ecfa24 100644 (file)
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -23567,6 +23567,12 @@ methods have a chance to execute at that location.  In this scenario
 if one of the methods returns @code{True} but the others return
 @code{False}, the inferior will still be stopped.
 
+You should not alter the execution state of the inferior (i.e.@:, step,
+next, etc.), alter the current frame context (i.e.@:, change the current
+active frame), or alter, add or delete any breakpoint.  As a general
+rule, you should not alter any data within @value{GDBN} or the inferior
+at this time.
+
 Example @code{stop} implementation:
 
 @smallexample