Fix documentation about rot agent expression bytecode
The rot agent expression bytecode rotates the three items on the top of the stack. It is not clear which way the rotation is. However, the documentation currently shows this as the effect of the instructions: a b c => c b a which doesn't make sense, since the value b doesn't move. The two valid possibilities I see are a b c => b c a a b c => c a b depending on which way you rotate. When looking at the gdbserver code, the top of the stack becomes the third item, and the next-to-top item becomes the top. So the second form would be the right one, since in this notation the top of the stack is the rightmost element: a b c => c a b I adjusted the symbolic description and added a bit of text to make it more obvious. gdb/doc/ChangeLog: * agentexpr.texi (rot): Fix symbolic description, improve textual description.
This commit is contained in:
parent
4bbd4ef219
commit
791fb3d7a5
@ -1,3 +1,8 @@
|
||||
2017-07-31 Simon Marchi <simon.marchi@ericsson.com>
|
||||
|
||||
* agentexpr.texi (rot): Fix symbolic description, improve
|
||||
textual description.
|
||||
|
||||
2017-07-26 Yao Qi <yao.qi@linaro.org>
|
||||
|
||||
* gdb.texinfo (Maintenance Commands): Document command
|
||||
|
@ -396,8 +396,10 @@ is zero, this is the same as @code{dup}; if @var{n} is one, it copies
|
||||
the item under the top item, etc. If @var{n} exceeds the number of
|
||||
items on the stack, terminate with an error.
|
||||
|
||||
@item @code{rot} (0x33): @var{a} @var{b} @var{c} => @var{c} @var{b} @var{a}
|
||||
Rotate the top three items on the stack.
|
||||
@item @code{rot} (0x33): @var{a} @var{b} @var{c} => @var{c} @var{a} @var{b}
|
||||
Rotate the top three items on the stack. The top item (c) becomes the third
|
||||
item, the next-to-top item (b) becomes the top item and the third item (a) from
|
||||
the top becomes the next-to-top item.
|
||||
|
||||
@item @code{if_goto} (0x20) @var{offset}: @var{a} @result{}
|
||||
Pop an integer off the stack; if it is non-zero, branch to the given
|
||||
|
Loading…
Reference in New Issue
Block a user