Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: ppmoore <polomora@gmail.com>
To: gdb@sources.redhat.com
Subject: Re: Debugging remotely via ssh login
Date: Tue, 26 Dec 2006 00:47:00 -0000	[thread overview]
Message-ID: <8050087.post@talk.nabble.com> (raw)
In-Reply-To: <8048624.post@talk.nabble.com>


Thanks Hadron.

I found this also, from a colleague at work, after I had posted.

Regards,
Paul



Hadron wrote:
> 
> Cant you just create a secure shell and run gdb.
> 
> You might find this interesting as I was looking into this recently.
> 
> http://www.cucy.net/lacp/archives/000024.html
> 
> 
> 
> 
> ppmoore wrote:
>> 
>> Hello, I wonder if anyone can help with with this one.
>> 
>> In our environment, we test by copying our executables to a destination
>> machine on our test network using scp, copy the set of source code files
>> that we are debugging to the same destination, and then log on to the
>> remote node using ssh to perform the debugging session.
>> 
>> I was reading in the manual about remote debugging, but the scenarios
>> described included debugging via a serial comm line or via a tcp port on
>> the remote machine. Is it possible to debug where the only access is
>> remote logon using ssh?
>> 
>> Many thanks,
>> Paul
>> 
> 
> 

-- 
View this message in context: http://www.nabble.com/Debugging-remotely-via-ssh-login-tf2869437.html#a8050087
Sent from the gdb - General mailing list archive at Nabble.com.


      reply	other threads:[~2006-12-26  0:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-22  7:08 ppmoore
2006-12-22 10:24 ` Andreas Schwab
2006-12-22 10:46   ` Eli Zaretskii
2006-12-22 17:53     ` Paul Koning
2006-12-25 20:09 ` Hadron
2006-12-26  0:47   ` ppmoore [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=8050087.post@talk.nabble.com \
    --to=polomora@gmail.com \
    --cc=gdb@sources.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