Make mi-break.exp always expect breakpoint commands output on the main UI
authorPedro Alves <palves@redhat.com>
Tue, 21 Jun 2016 00:11:56 +0000 (01:11 +0100)
committerPedro Alves <palves@redhat.com>
Tue, 21 Jun 2016 00:11:56 +0000 (01:11 +0100)
commitef274d26b57336b3baa5bb0ae93b49178bc45631
tree0977eee0d20b8976ca8fc43fb315e07a55bf9554
parent468afe6c5fc9c80b8c175f3f13702ffaa6308400
Make mi-break.exp always expect breakpoint commands output on the main UI

mi-break.exp regresses when tested with MI running on a secondary UI,
with RUNTESTFLAGS="FORCE_SEPARATE_MI_TTY=1".

The problem is simply that the test sets a breakpoint, and attaches
"print" commands to the breakpoint.  Since breakpoint commands always
run with the main UI as current UI, the breakpoint command's output
goes to the main UI.  So we need to tweak the test to expect it there.

gdb/testsuite/ChangeLog:
2016-06-21  Pedro Alves  <palves@redhat.com>

* gdb.mi/mi-break.exp (test_breakpoint_commands): Always expect
breakpoint command's output on the main UI.
(test_break): New procedure, factored out from calls in the top
level.
(top level): Use foreach_with_prefix to test MI as main UI and as
separate UI.
gdb/testsuite/ChangeLog
gdb/testsuite/gdb.mi/mi-break.exp