From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: ghost@cs.msu.su
Cc: gdb-patches@sources.redhat.com
Subject: Re: "target remote | " stderr
Date: Sun, 11 Feb 2007 18:10:00 -0000 [thread overview]
Message-ID: <200702111809.l1BI9cM8023458@brahms.sibelius.xs4all.nl> (raw)
In-Reply-To: <eqnhq8$8nt$1@sea.gmane.org> (message from Vladimir Prus on Sun, 11 Feb 2007 19:55:03 +0300)
> From: Vladimir Prus <ghost@cs.msu.su>
> Date: Sun, 11 Feb 2007 19:55:03 +0300
>
> Daniel Jacobowitz wrote:
>
> > On Wed, Jan 31, 2007 at 05:34:21PM +0300, Vladimir Prus wrote:
> >> Implementing for MinGW required modifying libiberty so that
> >> it can catch stderr to a pipe. Here's a patch for gdb that
> >> relies on the libiberty patch. Does this sound OK
> >> provided libiberty patch is approved?
> >
> > Do we automatically get a non-blocking pipe on mingw, or do we have to
> > set it ourselves?
>
> We have to set it ourself, unfortunately. I had one test case working
> fine, but got gdb hanging on some other.
>
> The attached patch works around the blocking issues, and more extensively
> tested. OK?
Please keep Windows-specific code out of ser-base.c. Is read() on
MinGW fully blocking? Or will it return whatever is available and
only block if nothing is available. Then you could use gdb_select()
to check whether input is available on the pipe.
Otherwise, you should think about introducing an asbtraction layer for
reading from error_fd.
Mark
next prev parent reply other threads:[~2007-02-11 18:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-26 13:54 Vladimir Prus
2007-01-26 14:00 ` Daniel Jacobowitz
2007-01-31 14:35 ` Vladimir Prus
2007-01-31 14:41 ` Daniel Jacobowitz
2007-02-11 16:56 ` Vladimir Prus
2007-02-11 18:10 ` Mark Kettenis [this message]
2007-02-17 7:50 ` Vladimir Prus
2007-02-11 20:24 ` Eli Zaretskii
2007-02-17 7:35 ` Vladimir Prus
2007-02-17 10:56 ` Eli Zaretskii
2007-02-17 14:31 ` Vladimir Prus
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=200702111809.l1BI9cM8023458@brahms.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=gdb-patches@sources.redhat.com \
--cc=ghost@cs.msu.su \
/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