From: Ben Elliston <bje@redhat.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: sid@sources.redhat.com
Subject: Re: (gdb) target remote |foo-elf-sid --stdio
Date: Thu, 18 Apr 2002 09:51:00 -0000 [thread overview]
Message-ID: <15550.63903.473019.742005@toenail.toronto.redhat.com> (raw)
In-Reply-To: <3CBEBC77.6090205@cygnus.com>
>>>>> "Andrew" == Andrew Cagney <ac131313@cygnus.com> writes:
Andrew> GDB's remote command supports a pipe mode (it's supported it for some
Andrew> years now). It lets GDB communicate with a sub-process using the remote
Andrew> protocol via that processes stdin/stdout. The command syntax is:
Andrew> (gdb) target remote |command to run with arguments
Andrew> Can SID be modified to support this mode? It is easier to script then
Andrew> the current: start sid; start gdb; connect.
Yes. In fact, I believe it was done once as a proof of concept.
Naturally, the standard input/output from a process emulation
component would need to be diverted to a Tk terminal window or some
other location so that it doesn't get interleaved with GDB protocol
chatter.
Andrew> (PS: As always, there could be teething problems in GDB)
Agreed.
Ben
prev parent reply other threads:[~2002-04-18 16:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-18 5:30 Andrew Cagney
2002-04-18 9:51 ` Ben Elliston [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=15550.63903.473019.742005@toenail.toronto.redhat.com \
--to=bje@redhat.com \
--cc=ac131313@cygnus.com \
--cc=sid@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).