[gdb/testsuite] Handle unordered dict in gdb.python/py-mi-cmd.exp
authorTom de Vries <tdevries@suse.de>
Tue, 14 Jun 2022 17:50:44 +0000 (19:50 +0200)
committerTom de Vries <tdevries@suse.de>
Tue, 14 Jun 2022 17:50:44 +0000 (19:50 +0200)
commit362a867f2ac16f597d06e8a9a3f6c15afa7adf6f
tree3746f969fad22b06e01b1cae84c24a75bc07dd58
parent965b71a7f739a747c6b427a96b1fa9dd26e38956
[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.
gdb/testsuite/gdb.python/py-mi-cmd.exp