Re: [PATCH fifo 0/2] Add support for duplex FIFOs

On Mar 26 17:24, Ken Brown wrote: > Hi Corinna, > > On 3/26/2019 4:36 AM, Corinna Vinschen wrote: > > Hi Ken, > > > > On Mar 25 23:06, Ken Brown wrote: > >> The second patch in this series enables opening a FIFO with O_RDWR > >> access. The underlying Windows named pipe is creted with duplex >

Re: [PATCH RFC] fork: reduce chances for "address space is already occupied" errors

On Mar 26 19:25, Corinna Vinschen wrote: > Hi Michael, > > > Redirected to cygwin-patches... > > > On Mar 26 18:10, Michael Haubenwallner wrote: > > Hi Corinna, > > > > as I do still encounter fork errors (address space needed by is > > already occupied) with dynamically loaded dlls (but

Re: [PATCH RFC] fork: reduce chances for "address space is already occupied" errors

Hi Michael, Redirected to cygwin-patches... On Mar 26 18:10, Michael Haubenwallner wrote: > Hi Corinna, > > as I do still encounter fork errors (address space needed by is > already occupied) with dynamically loaded dlls (but unrelated to > replaced dlls), one of them repeating even upon

Re: [PATCH fifo 0/2] Add support for duplex FIFOs

Hi Corinna, On 3/26/2019 4:36 AM, Corinna Vinschen wrote: > Hi Ken, > > On Mar 25 23:06, Ken Brown wrote: >> The second patch in this series enables opening a FIFO with O_RDWR >> access. The underlying Windows named pipe is creted with duplex >> access, and its handle is made the I/O handle of

Re: [PATCH fifo 0/2] Add support for duplex FIFOs

Hi Ken, On Mar 25 23:06, Ken Brown wrote: > The second patch in this series enables opening a FIFO with O_RDWR > access. The underlying Windows named pipe is creted with duplex > access, and its handle is made the I/O handle of the first client. > > While testing this, I had some mysterious