From: James Lemke <jim@wasabisystems.com>
To: insight@sourceware.org
Subject: Re: RFC: patch for insight & target stdin
Date: Wed, 11 May 2005 14:21:00 -0000 [thread overview]
Message-ID: <1115821266.24600.32.camel@keel.thelemkes.ca> (raw)
In-Reply-To: <42820FE7.8020702@redhat.com>
On Wed, 2005-05-11 at 10:00, Fernando Nasser wrote:
> Hi Jim,
>
> The reason I left this out was because it breaks on Windows (Cygwin), at
> least the code I had at the time broke with the Cygwin of that time...
>
> We need someone to test this on a Windows machine and see what happens.
Hi Fernando.
Do you mean Cygwin native? I did test on Cygwin x xscale-elf.
Jim.
> 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.
> >
> > Jim.
--
James Lemke jim@wasabisystems.com Orillia, Ontario
http://www.wasabisystems.com
next prev parent reply other threads:[~2005-05-11 14:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-10 20:46 James Lemke
2005-05-11 14:01 ` Fernando Nasser
2005-05-11 14:10 ` Dave Korn
2005-05-11 14:21 ` James Lemke [this message]
2005-05-17 13:23 ` James Lemke
2005-05-17 15:35 ` Keith Seitz
2005-05-27 1:56 ` Keith Seitz
2005-05-27 12:40 ` James Lemke
2005-05-27 15:57 ` Keith Seitz
2005-05-24 18:43 ` James Lemke
2005-05-24 18:50 ` Keith Seitz
2005-05-26 16:25 ` Multiple definition of `_solib_address' [was RE: RFC: patch for insight & target stdin] Dave Korn
2005-05-26 16:28 ` Keith Seitz
2005-05-26 16:32 ` Multiple definition of `_solib_address' [was RE: RFC: patchfor " Dave Korn
2005-05-26 16:34 ` Keith Seitz
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=1115821266.24600.32.camel@keel.thelemkes.ca \
--to=jim@wasabisystems.com \
--cc=insight@sourceware.org \
/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).