Need help with GDB test run: Asks for password although ssh setup not to require password.

Need help with GDB test run: Asks for password although ssh setup not to require password.

[Anmol P. Paralkar]

Hello,

  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. However, I see
  these failures in my gdb.log file:

-------------------------------------------------------------------------------- 
spawn ssh -l b07584 perf1vme6 gdbserver :4004 vmx21726.x^M
  b07584@perf1vme6's password: board_info host exists name
board_info host name
getting ld0159-tx32 name
board_info ld0159-tx32 exists name
board_info ld0159-tx32 exists protocol
board_info ld0159-tx32 generic_name
getting ld0159-tx32 generic_name
call_remote  send ld0159-tx32 {target remote perf1vme6:4004
}
board_info ld0159-tx32 file_transfer
getting ld0159-tx32 file_transfer
board_info ld0159-tx32 connect
getting ld0159-tx32 connect
looking for ld0159-tx32_send
looking for telnet_send
looking for standard_send
call_remote calling standard_send
board_info ld0159-tx32 exists fileid
board_info ld0159-tx32 fileid
getting ld0159-tx32 fileid
shell_id in standard_send is exp6
board_info ld0159-tx32 fileid
getting ld0159-tx32 fileid
send -i exp6 -- {target remote perf1vme6:4004
}
board_info ld0159-tx32 fileid
getting ld0159-tx32 fileid
board_info target exists gdb,timeout
board_info host fileid
getting ld0159-tx32 fileid
target remote perf1vme6:4004^M
perf1vme6:4004: Connection refused.^M
(gdb) Connection refused by remote target.  Pausing, and trying again.
--------------------------------------------------------------------------------

  The: "perf1vme6:4004: Connection refused" is due to the gdbserver not being up
  on the target and I think, that, in turn is due to the password being asked when:
  "spawn ssh -l b07584 perf1vme6 gdbserver :4004 hello" happens.

  If I run the ssh by hand, I am not asked for a password, I do see something like:

----------------------------------------
Process hello created; pid = 550
Listening on port 4004
----------------------------------------

  and I can remote connect and debug as given in the GDB User Manual.

  --

  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.

Thanks,
Anmol.

Re: Need help with GDB test run: Asks for password although ssh setup not to require password.

[Andreas Schwab]

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

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

Re: Need help with GDB test run: Asks for password although ssh setup not to require password.

[Anmol P. Paralkar]

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