aboutsummaryrefslogtreecommitdiff
path: root/gdb/gdb.gdb
diff options
context:
space:
mode:
authorAndrew Burgess <aburgess@redhat.com>2023-02-17 15:19:12 +0000
committerAndrew Burgess <aburgess@redhat.com>2023-02-28 10:56:28 +0000
commit292deeba7d6e0f1df99fff8c18000a1a3c481f3a (patch)
tree1faef9f4c1998fc631adb142b1f77b8561c3f72e /gdb/gdb.gdb
parent1ccc4abbb3dda91c94c54d3aaaa417f0d7740a3f (diff)
downloadgdb-292deeba7d6e0f1df99fff8c18000a1a3c481f3a.zip
gdb-292deeba7d6e0f1df99fff8c18000a1a3c481f3a.tar.gz
gdb-292deeba7d6e0f1df99fff8c18000a1a3c481f3a.tar.bz2
gdb/testsuite introduce foreach_mi_ui_mode helper proc
Introduce foreach_mi_ui_mode, a helper proc which can be used when tests are going to be repeated once with the MI in the main UI, and once with the MI on a separate UI. The proc is used like this: foreach_mi_ui_mode VAR { # BODY } The BODY will be run twice, once with VAR set to 'main' and once with VAR set to 'separate', inside BODY we can then change the behaviour based on the current UI mode. The point of this proc is that we sometimes shouldn't run the separate UI tests (when gdb_debug_enabled is true), and this proc hides all this logic. If the separate UI mode should not be used then BODY will be run just once with VAR set to 'main'. I've updated two tests that can make use of this helper proc. I'm going to add another similar test in a later commit. There should be no change to what is tested with this commit. Approved-By: Pedro Alves <pedro@palves.net>
Diffstat (limited to 'gdb/gdb.gdb')
0 files changed, 0 insertions, 0 deletions