This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH] A new board file remote-gdbserver-on-localhost.exp
- From: Sergio Durigan Junior <sergiodj at redhat dot com>
- To: Yao Qi <qiyaoltc at gmail dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Fri, 24 Apr 2015 15:38:59 -0400
- Subject: Re: [PATCH] A new board file remote-gdbserver-on-localhost.exp
- Authentication-results: sourceware.org; auth=none
- References: <1429796515-26821-1-git-send-email-qiyaoltc at gmail dot com>
On Thursday, April 23 2015, Yao Qi wrote:
> From: Yao Qi <yao.qi@linaro.org>
>
> This patch is to add a new board file that does real remote gdbserver
> testing on localhost. This board file can be used to reproduce PR 18208.
Thanks for this, Yao.
While using your board file to try to reproduce the failure, I found
that it can stale on:
(gdb) spawn /usr/bin/ssh -l user localhost
/path/to/gdb/build-original/gdb/testsuite/../gdbserver/gdbserver --once :2346
/path/to/gdb/build-original/gdb/testsuite/gdb.base/coredump-filter
The authenticity of host 'localhost (::1)' can't be established.
ECDSA key fingerprint is xx:xx:xx:xx:xx:xx.
Are you sure you want to continue connecting (yes/no)?
got a INT signal, interrupted by user
It also can stale if the user needs to provide a password to log into
the system (which normally is the case). BTW, how do you use the board
in this case?
*And* it also assumes that the user will have a sshd running on
localhost, which is not always the case, right?
So maybe the board could check for those cases and act accordingly, or
at least the introductory comments on the board file could be extended
to mention those situations.
Cheers,
--
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/