From: Michael Snyder <msnyder@redhat.com>
To: gdb@sources.redhat.com
Subject: Re: remote stdio
Date: Thu, 10 Jan 2002 17:30:00 -0000 [thread overview]
Message-ID: <3C3E3D84.52FEF644@redhat.com> (raw)
In-Reply-To: <200201101827.NAA423637035@node128.ott.qnx.com>
Graeme Peterson wrote:
>
> Hi, all.
>
> I have a remote stub working for QNX's remote debug server.
> The server manages stdin, out and err, however I am having
> trouble finding out how GDB shares the text console's stdin
> for a remote target.
It doesn't. The remote protocol has no provision for this.
> When the inferior is given free reign to run, and GDB winds up
> waiting for ever, what mechanisms exist to allow any subsequent
> keyboard input to be captured and sent to the remote target?
None.
> Basically, I want to respond to a getch() in the inferior, or
> run a 'vi' session in DDD's execution window via the remote
> target connection.
If you get it working, please submit it! ;-)
> What I have done so far is added the stdin fd to the fd set
> for the select() in ser_unix_wait_for (gdb/ser-unix.c). This
> works fine for TCP/IP connections, but the code path is not
> executed for serial connections. I would also prefer not
> to modify the generic GDB source files if a mechanism exists
> that I can take advantage of.
Sorry, you are going to have to
1) Extend the remote protocol, and
2) extend gdb.
next prev parent reply other threads:[~2002-01-11 1:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-10 10:27 Graeme Peterson
2002-01-10 17:30 ` Michael Snyder [this message]
2002-01-10 18:16 ` Andrew Cagney
2002-01-10 18:46 ` gp
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=3C3E3D84.52FEF644@redhat.com \
--to=msnyder@redhat.com \
--cc=gdb@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