From: Daniel Jacobowitz <drow@false.org>
To: James Lemke <jim@wasabisystems.com>
Cc: gdb@sources.redhat.com
Subject: Re: RFC: patch for insight & target stdin
Date: Tue, 10 May 2005 20:32:00 -0000 [thread overview]
Message-ID: <20050510203232.GA10672@nevyn.them.org> (raw)
In-Reply-To: <1115757054.24600.14.camel@keel.thelemkes.ca>
On Tue, May 10, 2005 at 04:30:54PM -0400, James Lemke wrote:
> I had a customer complaint about insight, that target programs could
> write to stdout but not read from stdin. On Linux, stdout went to the
> console window and stdin came from the launch shell. On Windows stdout
> went to the console window and stdin just failed with EBADF.
>
> Apparently this was never implemented, so I made an attempt. Reads from
> stdin now come from the console window. This has been tested with
> x86-linux x xscale-elf and cygwin x xscale-elf.
>
> I don't know gdb / gdbtk implementation well, so I'm open to comments.
Insight has its own mailing list and is not part of GDB; I recommend
you send this to insight@sourceware.org instead.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-05-10 20:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-10 20:31 James Lemke
2005-05-10 20:32 ` Daniel Jacobowitz [this message]
2005-05-10 20:36 ` James Lemke
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=20050510203232.GA10672@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=jim@wasabisystems.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