From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: Mark Geisert <mark@maxrnd.com>
Cc: cygwin@cygwin.com
Subject: Re: Patch request to qt 5.9.4 (Re: [ANNOUNCEMENT] Qt 5.9.4)
Date: Mon, 11 Mar 2019 09:45:00 -0000 [thread overview]
Message-ID: <20190311094503.GC3785@calimero.vinschen.de> (raw)
In-Reply-To: <30cae96a-7c70-5634-85ce-3fe6b36a7d21@maxrnd.com>
[-- Attachment #1: Type: text/plain, Size: 1053 bytes --]
On Mar 11 00:21, Mark Geisert wrote:
> Tatsuro MATSUOKA wrote:
> > [...]
> > without the above patch ()
> > qt_safe_socket(PF_UNIX, SOCK_STREAM, 0, O_NONBLOCK)))
> > gnuplot cannot connect with gnuplot_qt.
> >
> > with the above patch ()
> > qt_safe_socket(PF_UNIX, SOCK_STREAM, 0))
> > gnuplot can connect with gnuplot_qt.
> >
> > Perhaps qt with O_NONBLOCK is some wrong with process connection.
>
> Hi Tatsuro,
> For the record, what Enrico supplied is what we'd call an STC, a Simple Test
> Case. Unfortunately his STC dealt with select() on a named pipe.
>
> Your gnuplot issue has to do with "Unix sockets", a form of IPC between
> processes. Cygwin uses Windows named pipes to implement "Unix sockets" on
> Windows.
No, wait! While there is code in Cygwin which is supposed to use
Windows named pipes to implement AF_UNIX sockets at one point, thos
code is far from being complete.
As yet, Cygwin uses loopback IPv4 sockets to implement AF_UNIX sockets.
Corinna
--
Corinna Vinschen
Cygwin Maintainer
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-03-11 9:45 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1439412702.1866573.1551653028041.JavaMail.yahoo.ref@mail.yahoo.co.jp>
2019-03-03 22:43 ` Tatsuro MATSUOKA
2019-03-04 16:32 ` Yaakov Selkowitz
2019-03-04 22:29 ` Tatsuro MATSUOKA
2019-03-05 12:57 ` Tatsuro MATSUOKA
2019-03-05 19:24 ` Achim Gratz
2019-03-05 23:58 ` Tatsuro MATSUOKA
2019-03-06 0:10 ` Tatsuro MATSUOKA
2019-03-06 1:10 ` Tatsuro MATSUOKA
2019-03-06 1:55 ` Tatsuro MATSUOKA
2019-03-06 2:25 ` Tatsuro MATSUOKA
2019-03-11 0:28 ` Tatsuro MATSUOKA
2019-03-11 0:50 ` Andrey Repin
2019-03-11 0:53 ` Yaakov Selkowitz
2019-03-11 3:33 ` Tatsuro MATSUOKA
2019-03-11 7:21 ` Mark Geisert
2019-03-11 7:56 ` Tatsuro MATSUOKA
2019-03-12 4:21 ` Mark Geisert
2019-03-12 6:51 ` Tatsuro MATSUOKA
2019-03-12 8:04 ` Patch request to qt 5.9.4 Mark Geisert
2019-03-12 8:26 ` Tatsuro MATSUOKA
2019-03-12 19:37 ` Achim Gratz
2019-03-12 23:22 ` Tatsuro MATSUOKA
2019-03-13 1:12 ` Mark Geisert
2019-03-13 4:27 ` Tatsuro MATSUOKA
2019-03-13 8:33 ` Mark Geisert
2019-03-15 8:06 ` Mark Geisert
2019-03-15 9:40 ` Tatsuro MATSUOKA
2019-03-16 0:41 ` Tatsuro MATSUOKA
2019-03-12 19:34 ` Achim Gratz
2019-03-11 9:45 ` Corinna Vinschen [this message]
2019-03-12 4:16 ` Patch request to qt 5.9.4 (Re: [ANNOUNCEMENT] Qt 5.9.4) Mark Geisert
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=20190311094503.GC3785@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin@cygwin.com \
--cc=mark@maxrnd.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).