On Wed, Apr 21, 2004 at 11:50:59AM +0200, Corinna Vinschen [EMAIL PROTECTED] wrote:
On Apr 21 02:36, Yitzchak Scott-Thoennes wrote:
On Wed, Apr 21, 2004 at 10:46:59AM +0200, Corinna Vinschen [EMAIL PROTECTED]
wrote:
Did you try it with a recent Cygwin version? I used your above test
On Apr 21 02:36, Yitzchak Scott-Thoennes wrote:
On Wed, Apr 21, 2004 at 10:46:59AM +0200, Corinna Vinschen [EMAIL PROTECTED] wrote:
Did you try it with a recent Cygwin version? I used your above test
application and I'm getting a EPIPE (resp. a SIGPIPE) as expected.
I think I had heard
On Apr 20 18:17, Yitzchak Scott-Thoennes wrote:
This seems to be the cause of perl's ext/Socket/t/socketpair.t test 14
failing (which I've seen since at least 1.3.22).
$ cat pairsock.c
#include stdio.h
#include sys/socket.h
#include unistd.h
int main (int argc, char **argv) {
int
On Wed, Apr 21, 2004 at 10:46:59AM +0200, Corinna Vinschen [EMAIL PROTECTED] wrote:
Did you try it with a recent Cygwin version? I used your above test
application and I'm getting a EPIPE (resp. a SIGPIPE) as expected.
I think I had heard that others were not seeing this failure. I'm
This seems to be the cause of perl's ext/Socket/t/socketpair.t test 14
failing (which I've seen since at least 1.3.22).
$ cat pairsock.c
#include stdio.h
#include sys/socket.h
#include unistd.h
int main (int argc, char **argv) {
int sockets[2] = {-1, -1};
int result;
ssize_t wrote;
5 matches
Mail list logo