Re: [PATCH 5/6] testsuite: Introduce $inferior_spawn_id

[Yao Qi <qiyaoltc@gmail.com>]

Pedro Alves <palves@redhat.com> writes:

Hi Pedro,

> +	# GDBserver doesn't do inferior I/O through GDB.  But we can
> +	# talk to the program using GDBserver's tty instead.
> +	global inferior_spawn_id
> +	set inferior_spawn_id $server_spawn_id

Does it still work well if GDBserver is started without tty?  In my
remote testing, gdbserver is started without tty,

spawn /usr/bin/ssh -l yao junor1 /gdbserver/aarch64/gdbserver --once :2346 aarch64-linux-gnu/gdb/testsuite/gdb.base/interrupt

I see the following timeouts:

Continuing.^M
Remote debugging from host 10.2.206.34^M
FAIL: gdb.base/interrupt.exp: process is alive (timeout)
a^M
a^M
FAIL: gdb.base/interrupt.exp: child process ate our char (timeout)

We need to override ${board}_spawn and pass "-t" to ssh.  After this change,
all interrupt.exp tests pass.  Since the test harness assumes GDBserver
has tty, probably we should document such requirement somewhere.

However, I don't run the whole testsuite with the updated board file
(with -t option to ssh).

-- 
Yao (齐尧)