diff options
| author | Pedro Alves <palves@redhat.com> | 2016-06-21 01:11:55 +0100 |
|---|---|---|
| committer | Pedro Alves <palves@redhat.com> | 2016-06-21 01:11:55 +0100 |
| commit | 51f77c3704a6e5c28fdcdd6d6e0aeb97ebdb343f (patch) | |
| tree | 734f6ec6ef32bede4aafad4614cc2f77d95e5d93 /gdb/testsuite/README | |
| parent | 86f78169c82095eced3a4d1b30f8e002ec841d79 (diff) | |
| download | gdb-51f77c3704a6e5c28fdcdd6d6e0aeb97ebdb343f.zip gdb-51f77c3704a6e5c28fdcdd6d6e0aeb97ebdb343f.tar.gz gdb-51f77c3704a6e5c28fdcdd6d6e0aeb97ebdb343f.tar.bz2 | |
Add testing infrastruture bits for running with MI on a separate UI
With this, a specific test may can start GDB with MI on a separate UI
by using:
mi_gdb_start separate-mi-tty
In addition, it's also possible to run the whole testsuite with MI on
a separate tty, with:
make check RUNTESTFLAGS="FORCE_SEPARATE_MI_TTY=1"
gdb_main_spawn_id and mi_spawn_id are added so that tests may expect
output from either channel.
While at it, inferior_spawn_id was not being cleared when gdb exits,
unlike the other spawn ids, thus a test that starts gdb more than once
would end up using a stale spawn id.
gdb/testsuite/ChangeLog:
2016-06-21 Pedro Alves <palves@redhat.com>
* README (Testsuite Parameters): Document FORCE_SEPARATE_MI_TTY.
* lib/gdb.exp (default_gdb_exit): Clear inferior_spawn_id.
* lib/mi-support.exp (mi_uncatched_gdb_exit): Unset
gdb_main_spawn_id, mi_spawn_id, unset inferior_spawn_id.
(gdb_main_spawn_id, mi_spawn_id): Declare and
comment.
(mi_create_inferior_pty): New procedure,
factored out from default_mi_gdb_start.
(switch_gdb_spawn_id, mi_gdb_start_separate_mi_tty): New
procedures.
(default_mi_gdb_start): Call mi_gdb_start_separate_mi_tty if the
separate-mi-tty option is specified, or SEPARATE_MI_TTY is set.
Use mi_create_inferior_pty.
(mi_gdb_start): Use eval to pass down args list.
Diffstat (limited to 'gdb/testsuite/README')
| -rw-r--r-- | gdb/testsuite/README | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/gdb/testsuite/README b/gdb/testsuite/README index 043a8bd..152318a 100644 --- a/gdb/testsuite/README +++ b/gdb/testsuite/README @@ -208,6 +208,12 @@ FORCE_PARALLEL Setting FORCE_PARALLEL to any non-empty value forces parallel testing mode even if RUNTESTFLAGS is not empty. +FORCE_SEPARATE_MI_TTY + +Setting FORCE_MI_SEPARATE_UI to 1 forces all MI testing to start GDB +in console mode, with MI running on a separate TTY, on a secondary UI +started with "new-ui". + GDB_INOTIFY For debugging parallel mode, it is handy to be able to see when a test |