From: Kris Warkentin <kewarken@qnx.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: yuri@enmediainc.com, gdb@sourceware.org
Subject: Re: Multiplexing gdb remote protocol and application output
Date: Wed, 21 Sep 2005 14:34:00 -0000 [thread overview]
Message-ID: <43317076.8050805@qnx.com> (raw)
In-Reply-To: <20050921025532.GA5927@nevyn.them.org>
Daniel Jacobowitz wrote:
> On Tue, Sep 20, 2005 at 05:58:29PM -0700, yuri@enmediainc.com wrote:
> > Hello,
> >
> > Older gdb versions supported 'target cisco'. Function readsocket()
> allowed
> > to distinct between application output and remote communication
> protocol
> > packets, using escape sequence.
> >
> > Now 'target cisco' support removed from gdb distribution. Is there any
> > standard way in gdb to multiplex remote protocol and application
> > input/output?
>
> Not really, but there's at least one tool that can do this, called kdmx
> (specific to Linux but I believe it ought to be fairly portable).
>
> I'm afraid that's all I know about the subject though.
>
Our QNX pdebug protocol does it by defining different communication
channels for protocol messages and I/O. The support isn't rolled into
the FSF tree yet however and there aren't any clients other than
Neutrino. Wow. How incredibly unhelpful of me. ;-)
I know that Cisco has their support ported to newer versions of gdb but
I hadn't realized that they once had support in the main tree. I guess
they haven't gotten around to putting it back in.
cheers,
Kris
--
Stay up-to-date on all the QNX news! Register at
http://www.qnx.com/news/forms/newsletter.html to
receive our newsletter.
next prev parent reply other threads:[~2005-09-21 14:34 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 [this message]
2005-09-24 0:36 ` Yuri Karlsbrun
2005-09-21 13:35 ` Paul Koning
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=43317076.8050805@qnx.com \
--to=kewarken@qnx.com \
--cc=drow@false.org \
--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