On Jun 20 16:59, Marco Atzeri wrote: > Hi, > > trying to debug why recent postgresql code is failing only on > cygwin64 (all other platform and cygwin 32 are fine) > > $ uname -vrm > 1.7.30(0.272/5/3) 2014-05-23 10:36 x86_64 > > I noticed this strange output in the strace log > > 102 6076 [main] pg_regress 8200 transport_layer_pipes::connect: Try to > connect to named pipe: \\.\pipe\cygwin-0eb90a57d5759b7b-lpc > 115 6191 [main] pg_regress 8200 transport_layer_pipes::connect: Try to > connect to named pipe: \\.\pipe\cygwin-0eb90a57d5759b7b-lpc > 600 6791 [main] pg_regress 8200 transport_layer_pipes::write: error > writing to pipe, error = 233 > 27 6818 [main] pg_regress 8200 __set_errno: virtual ssize_t > transport_layer_pipes::write(void*, size_t):223 setting errno 22 > 28 6846 [main] pg_regress 8200 client_request::send: request body > write failure: only 18446744073709551615 bytes sent of 36, error = 22(233) > ^^^ ?
8 byte signed integer -1, accidentally printed as unsigned value. I fixed that in CVS. Write returned -1 here because the pipe write returned an error code 233, ERROR_PIPE_NOT_CONNECTED. It looks like the client process died for some reason. This reason is not visible in the output of cygserver, of course. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat
pgpWrlNzwpbq9.pgp
Description: PGP signature
