From: Paul Koning <pkoning@equallogic.com>
To: yuri@enmediainc.com
Cc: gdb@sourceware.org
Subject: Re: Multiplexing gdb remote protocol and application output
Date: Wed, 21 Sep 2005 13:35:00 -0000 [thread overview]
Message-ID: <17201.24991.338637.7754@gargle.gargle.HOWL> (raw)
In-Reply-To: <16928.66.129.224.36.1127264309.squirrel@66.129.224.36>
>>>>> "yuri" == yuri <yuri@enmediainc.com> writes:
yuri> Hello, Older gdb versions supported 'target cisco'. Function
yuri> readsocket() allowed to distinct between application output and
yuri> remote communication protocol packets, using escape sequence.
yuri> Now 'target cisco' support removed from gdb distribution. Is
yuri> there any standard way in gdb to multiplex remote protocol and
yuri> application input/output?
Output, yes; there's an encoding for output characters mentioned in
the remote protocol spec. Input, I don't think so.
paul
next prev parent reply other threads:[~2005-09-21 13:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-21 0:58 yuri
2005-09-21 2:55 ` Daniel Jacobowitz
2005-09-21 14:34 ` Kris Warkentin
2005-09-24 0:36 ` Yuri Karlsbrun
2005-09-21 13:35 ` Paul Koning [this message]
2005-09-21 17:01 ` Paul Gilliam
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=17201.24991.338637.7754@gargle.gargle.HOWL \
--to=pkoning@equallogic.com \
--cc=gdb@sourceware.org \
--cc=yuri@enmediainc.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).