Make testing gdb with FORCE_SEPARATE_MI_TTY=1 actually work
authorPedro Alves <palves@redhat.com>
Thu, 30 Jun 2016 10:55:21 +0000 (11:55 +0100)
committerPedro Alves <palves@redhat.com>
Thu, 30 Jun 2016 10:55:21 +0000 (11:55 +0100)
commit994e9c834d916af85e0fe0e8c3e18259aa4be389
treee00478e7dc72c54ee8401c388bfbda4c07322433
parent9004b6bd58b6203cb3d1de1ca8d6ce6fc140ae61
Make testing gdb with FORCE_SEPARATE_MI_TTY=1 actually work

Runing the whole gdb testsuite with MI on a separate tty, with:

  make check RUNTESTFLAGS="FORCE_SEPARATE_MI_TTY=1"

Doesn't actually work because commit 51f77c3704a6 ("Add testing
infrastruture bits for running with MI on a separate UI") included a
last-minute rename typo, now fixed with this commit.

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

* lib/mi-support.exp (default_mi_gdb_start): Declare global
FORCE_SEPARATE_MI_TTY, not SEPARATE_MI_TTY.
gdb/testsuite/ChangeLog
gdb/testsuite/lib/mi-support.exp