yggdrasil/binutils-gdb
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

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

Browse Source 
PR python/12930
	PR python/12802

	* gdb.texinfo (Breakpoints In Python): Clarify behavior in the
	stop method.
This commit is contained in:
Phil Muldoon 2011-10-07 13:23:18 +00:00
parent 03583c206f
commit 99f5279d98
2 changed files with 14 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
gdb/doc/ChangeLog
View File

@ -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"

6
gdb/doc/gdb.texinfo
View File

@ -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