diff options
| author | Simon Marchi <simon.marchi@ericsson.com> | 2017-07-31 11:22:21 +0200 |
|---|---|---|
| committer | Simon Marchi <simon.marchi@ericsson.com> | 2017-07-31 11:26:50 +0200 |
| commit | 791fb3d7a58b86e5f30229625dfd33659f33fd6e (patch) | |
| tree | 09af719651ef481436b871e46bce5cf5729dfce5 /gdb/doc/ChangeLog | |
| parent | 4bbd4ef219c5b4c7d437618ba8937af86dd1032e (diff) | |
| download | gdb-791fb3d7a58b86e5f30229625dfd33659f33fd6e.zip gdb-791fb3d7a58b86e5f30229625dfd33659f33fd6e.tar.gz gdb-791fb3d7a58b86e5f30229625dfd33659f33fd6e.tar.bz2 | |
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.
Diffstat (limited to 'gdb/doc/ChangeLog')
| -rw-r--r-- | gdb/doc/ChangeLog | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog index d43ae35..6a3d061 100644 --- a/gdb/doc/ChangeLog +++ b/gdb/doc/ChangeLog @@ -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 |