Re: Incorrect behavior in TIOCINQ ioctl

2020-03-02 Thread Corinna Vinschen
On Feb 29 11:37, Åke Rehnman wrote: > > On 2020-02-28 20:23, Corinna Vinschen wrote: > > > - Is it a safe bet that ClearCommError returns valid values in > >st.cbInQue even if one of the error conditions occur? Maybe the > >right thing to do is to return 0 in certain error cases...? > >

Re: Incorrect behavior in TIOCINQ ioctl

2020-02-29 Thread Åke Rehnman
On 2020-02-28 20:23, Corinna Vinschen wrote: - Is it a safe bet that ClearCommError returns valid values in st.cbInQue even if one of the error conditions occur? Maybe the right thing to do is to return 0 in certain error cases...? The win32 api  documentation does not mention anythin

Re: Incorrect behavior in TIOCINQ ioctl

2020-02-28 Thread Corinna Vinschen
On Feb 27 22:38, Åke Rehnman wrote: > Hi, > > I recently ran in to some troubles with the TIOCINQ ioctl. I am wondering if > the cygwin implementation is correct... It seems if there were any existing > framing overrun errors etc etc  before calling the TIOCINQ ioctl it is > returning an error (EI

Incorrect behavior in TIOCINQ ioctl

2020-02-27 Thread Åke Rehnman
Hi, I recently ran in to some troubles with the TIOCINQ ioctl. I am wondering if the cygwin implementation is correct... It seems if there were any existing framing overrun errors etc etc  before calling the TIOCINQ ioctl it is returning an error (EINVAL). Reading through linux implmentation