Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Yao Qi <qiyaoltc@gmail.com>
To: Sergio Durigan Junior <sergiodj@redhat.com>
Cc: Yao Qi <qiyaoltc@gmail.com>,  gdb-patches@sourceware.org
Subject: Re: [PATCH] A new board file remote-gdbserver-on-localhost.exp
Date: Tue, 28 Apr 2015 10:43:00 -0000	[thread overview]
Message-ID: <86vbggwovz.fsf@gmail.com> (raw)
In-Reply-To: <87zj5xco4s.fsf@redhat.com> (Sergio Durigan Junior's message of	"Fri, 24 Apr 2015 15:38:59 -0400")

Sergio Durigan Junior <sergiodj@redhat.com> writes:

> 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?

You need to use the right private key to access localhost without typing
password or passphrase.  In your ~/.ssh/config,

Host localhost
        IdentityFile ~/.ssh/id_rsa_phraseless
Host 127.0.0.1
        IdentityFile ~/.ssh/id_rsa_phraseless

>
> *And* it also assumes that the user will have a sshd running on
> localhost, which is not always the case, right?
>

Well, it is reasonable to have sshd running on a gdb dev box.

> 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.

Yes, I've added some comments into it.

-- 
Yao (齐尧)

From: Yao Qi <yao.qi@linaro.org>
Date: Tue, 28 Apr 2015 10:59:04 +0100
Subject: [PATCH] Add comments on using board file  remote-gdbserver-on-localhost.exp

This commit is to add comments on using this board file and the
requirements on localhost.

gdb/testsuite:

2015-04-28  Yao Qi  <yao.qi@linaro.org>

	* boards/remote-gdbserver-on-localhost.exp: Add comments.

diff --git a/gdb/testsuite/boards/remote-gdbserver-on-localhost.exp b/gdb/testsuite/boards/remote-gdbserver-on-localhost.exp
index 6a42b90..138782c 100644
--- a/gdb/testsuite/boards/remote-gdbserver-on-localhost.exp
+++ b/gdb/testsuite/boards/remote-gdbserver-on-localhost.exp
@@ -27,6 +27,9 @@ set_board_info compiler  "[find_gcc]"
 
 process_multilib_options ""
 
+# The sshd should be running on localhost and ssh key should be
+# correctly set up that you ssh to localhost without having to type
+# password.
 set_board_info rcp_prog "/usr/bin/scp"
 set_board_info rsh_prog "/usr/bin/ssh"
 set_board_info protocol standard


  reply	other threads:[~2015-04-28 10:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-23 13:42 Yao Qi
2015-04-23 15:18 ` Pedro Alves
2015-04-24 10:06   ` Yao Qi
2015-04-24 19:39 ` Sergio Durigan Junior
2015-04-28 10:43   ` Yao Qi [this message]
2015-06-22 13:03     ` Yao Qi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86vbggwovz.fsf@gmail.com \
    --to=qiyaoltc@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=sergiodj@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox