diff options
author | Tom de Vries <tdevries@suse.de> | 2022-06-14 19:50:44 +0200 |
---|---|---|
committer | Tom de Vries <tdevries@suse.de> | 2022-06-14 19:50:44 +0200 |
commit | 362a867f2ac16f597d06e8a9a3f6c15afa7adf6f (patch) | |
tree | 3746f969fad22b06e01b1cae84c24a75bc07dd58 /gdbserver/linux-s390-tdesc.h | |
parent | 965b71a7f739a747c6b427a96b1fa9dd26e38956 (diff) | |
download | gdb-362a867f2ac16f597d06e8a9a3f6c15afa7adf6f.zip gdb-362a867f2ac16f597d06e8a9a3f6c15afa7adf6f.tar.gz gdb-362a867f2ac16f597d06e8a9a3f6c15afa7adf6f.tar.bz2 |
[gdb/testsuite] Handle unordered dict in gdb.python/py-mi-cmd.exp
When running test-case gdb.python/py-mi-cmd.exp on openSUSE Leap 42.3 with
python 3.4, I occasionally run into:
...
Expecting: ^(-pycmd dct[^M
]+)?(\^done,result={hello="world",times="42"}[^M
]+[(]gdb[)] ^M
[ ]*)
-pycmd dct^M
^done,result={times="42",hello="world"}^M
(gdb) ^M
FAIL: gdb.python/py-mi-cmd.exp: -pycmd dct (unexpected output)
...
The problem is that the data type used here in py-mi-cmd.py:
...
elif argv[0] == "dct":
return {"result": {"hello": "world", "times": 42}}
...
is a dictionary, and only starting version 3.6 are dictionaries insertion
ordered, so using PyDict_Next in serialize_mi_result doesn't guarantee a
fixed order.
Fix this by allowing the alternative order.
Tested on x86_64-linux.
Diffstat (limited to 'gdbserver/linux-s390-tdesc.h')
0 files changed, 0 insertions, 0 deletions