Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: "KONG, Gangfeng" <gkong@IPRG.nokia.com>
Cc: Quality Quorum <qqi@theworld.com>,
	Andrew Cagney <ac131313@ges.redhat.com>,
	gdb@sources.redhat.com
Subject: Re: Remote target behind console server
Date: Fri, 28 Jun 2002 21:29:00 -0000	[thread overview]
Message-ID: <20020629042856.GA25124@nevyn.them.org> (raw)
In-Reply-To: <5.1.0.14.1.20020628183650.02b3c6b0@mailhost.iprg.nokia.com>

On Fri, Jun 28, 2002 at 06:45:17PM -0700, KONG, Gangfeng wrote:
> 
> >
> >>
> >> You mean an ``annex[tm]''?  Yes.  You'll likely need to tweak things so
> >> that  the terminal server automatically connects the GDB session through
> >> to the serial port.  There isn't an easy way, from GDB, to send terminal
> >> server commands.
> >
> >You have to configure your terminal server appropriately (either enable
> >'raw' mode on the terminal server or disable 'X' command on the stub/gdb)
> >and this is basically it, people do it all the time.
> >
> >If you are going to do 'load' over this connection big terminal server
> >buffers may screw it up.
> Thanks for your message,
> 
> Basically I need to use 'telnet' to the ip-addr of my terminal server to 
> access
> the serial port of my target box. I may reconfigure the terminal server, but
> how can I let gdb to setup an telnet connection to the terminal server and
> then take this connection as media for its serial access to the stub on
> the target?

Have you tried using 'target remote ip-addr:port' to the terminal
server directly?

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2002-06-29  4:29 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-27 18:12 KONG, Gangfeng
2002-06-28 15:49 ` Andrew Cagney
2002-06-28 17:51   ` Quality Quorum
     [not found]   ` <Pine.SGI.4.40.0206282044520.3477647-100000@shell01.TheWorl d.com>
2002-06-28 18:45     ` KONG, Gangfeng
2002-06-28 21:29       ` Daniel Jacobowitz [this message]
2002-07-02 20:05         ` KONG, Gangfeng
2002-07-02 21:40           ` Quality Quorum
2002-07-03  8:40           ` Andrew Cagney
2002-07-03 18:22             ` KONG, Gangfeng
     [not found]           ` <Pine.SGI.4.40.0207030038590.3981310-100000@shell01.TheWorl d.com>
2002-07-03 18:26             ` KONG, Gangfeng
2002-07-03 21:33               ` Quality Quorum
2002-07-03 21:55                 ` Eli Zaretskii
2002-07-08  9:49                   ` Andrew Cagney
     [not found]               ` <Pine.SGI.4.40.0207040021350.4215142-100000@shell01.TheWorl d.com>
2002-07-04 15:01                 ` KONG, Gangfeng
2002-07-04 22:21                   ` Quality Quorum
     [not found]                   ` <Pine.SGI.4.40.0207050115590.4236760-100000@shell01.TheWorl d.com>
2002-07-05 13:56                     ` KONG, Gangfeng
2002-07-05 16:21                       ` Quality Quorum
2002-06-29  7:45       ` Quality Quorum

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=20020629042856.GA25124@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=ac131313@ges.redhat.com \
    --cc=gdb@sources.redhat.com \
    --cc=gkong@IPRG.nokia.com \
    --cc=qqi@theworld.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