Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] A new board file remote-gdbserver-on-localhost.exp
Date: Fri, 24 Apr 2015 19:39:00 -0000	[thread overview]
Message-ID: <87zj5xco4s.fsf@redhat.com> (raw)
In-Reply-To: <1429796515-26821-1-git-send-email-qiyaoltc@gmail.com> (Yao Qi's	message of "Thu, 23 Apr 2015 14:41:55 +0100")

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/


  parent reply	other threads:[~2015-04-24 19:39 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 [this message]
2015-04-28 10:43   ` Yao Qi
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=87zj5xco4s.fsf@redhat.com \
    --to=sergiodj@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=qiyaoltc@gmail.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