Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Anmol P. Paralkar" <b07584@freescale.com>
To: Andreas Schwab <schwab@suse.de>
Cc: gdb@sourceware.org
Subject: Re: Need help with GDB test run: Asks for password although ssh  setup  not to require password.
Date: Tue, 28 Oct 2008 23:08:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.64.0810281749270.1412@ld0159-tx32> (raw)
In-Reply-To: <jebpx7lr0n.fsf@sykes.suse.de>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: TEXT/PLAIN; CHARSET=X-UNKNOWN; FORMAT=flowed, Size: 2060 bytes --]

On Sun, 26 Oct 2008, Andreas Schwab wrote:

> "Anmol P. Paralkar" <b07584@freescale.com> writes:
>
>>  I am trying to setup GDB DejaGNU remote testing using gdbserver. I have set things up so
>>  that I can ssh to my target machine without it asking for my password.
>
> Which method did you use for that?

  I had used: http://www.debian.org/devel/passwordlessssh

  but please read on, below.

>
>>  Is the failure I am seeing in the DejaGNU run really due to the gdbserver not being
>>  up prior to the remote connect attempt on the hostside GDB in turn, due to the password
>>  being asked on the ssh? What am I doing wrong here? Kindly help.
>
> Most likely some environment variables are lost, maybe SSH_AUTH_SOCK.
>
> Andreas.
>
> -- 
> Andreas Schwab, SuSE Labs, schwab@suse.de
> SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
> PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
> "And now for something completely different."
>

  I was using instructions from:

  http://www.stlinux.com/docs/manual/development/advanced_development12.php

  In particular, I needed to make this change:

--------------------------------------------------------------------------------
--- dejagnu-1.4.4-orig/lib/remote.exp   2003-10-11 07:42:46.000000000 +0100
+++ dejagnu-1.4.4/lib/remote.exp        2005-01-05 14:46:44.635002000 +0000
@@ -865,7 +865,8 @@
if ![board_info $dest exists username] {
set rsh_useropts ""
} else {
-        set rsh_useropts "-l $username"
+        set username [board_info $dest username]
+        set rsh_useropts "-l$username"
}

if [board_info $dest exists hostname] {
--------------------------------------------------------------------------------

  I hand-patched (lesson learnt!), and ended up overlooking the space (between the -l and $username)
  as I made the change, and got the "Connection refused"'s. I do not see the problem after having
  taken care of that.

  Thank you very much for your response.

Best Regards,
Anmol.

      reply	other threads:[~2008-10-28 23:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-26  1:25 Anmol P. Paralkar
2008-10-26  8:07 ` Andreas Schwab
2008-10-28 23:08   ` Anmol P. Paralkar [this message]

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=Pine.LNX.4.64.0810281749270.1412@ld0159-tx32 \
    --to=b07584@freescale.com \
    --cc=gdb@sourceware.org \
    --cc=schwab@suse.de \
    /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