From: "Kris Warkentin" <kewarken@qnx.com>
To: "Michael Elizabeth Chastain" <mec@shout.net>,
<gdb@sources.redhat.com>, <Gusti@pallas.dk>
Subject: Re: remote debugging on one serial line
Date: Fri, 17 Jan 2003 19:07:00 -0000 [thread overview]
Message-ID: <067301c2be5b$a243d110$0202040a@catdog> (raw)
In-Reply-To: <200301171844.h0HIiou04294@duracef.shout.net>
> Hello Agust,
>
> > I.e. I have to use the same line for console (minicom), file transfer
> > (rzsz) and remote gdb with gdbserver. My question is: has anybody been
> > successfull in doing that and if so how?
>
> Perhaps you could run ppp on the serial line to get to TCP/IP protocol.
> Then use telnet for the console access, ftp for the file transfer,
> and normal TCP/IP for gdb server.
This is the solution we recommend to our customers who debug over serial and
we've found it to be very successful (except for the pain of setting up ppp
but ymmv ;-)
Kris
next prev parent reply other threads:[~2003-01-17 19:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-17 18:44 Michael Elizabeth Chastain
2003-01-17 19:07 ` Kris Warkentin [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-20 8:08 Agust Karlsson
2003-01-17 10:10 Agust Karlsson
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='067301c2be5b$a243d110$0202040a@catdog' \
--to=kewarken@qnx.com \
--cc=Gusti@pallas.dk \
--cc=gdb@sources.redhat.com \
--cc=mec@shout.net \
/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