Re: Madness with the 'select' function, sigalrm, and stdout. (CYGWIN_NT-6.1-WOW64)

Larry Hall (Cygwin cygwin.com> writes: > So you're saying the snapshot exhibits the above behavior? > No, this was happening pre and post snapshot. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com

Re: Madness with the 'select' function, sigalrm, and stdout. (CYGWIN_NT-6.1-WOW64)

On 1/17/2012 6:24 PM, Robert F wrote: Larry Hall (Cygwin cygwin.com> writes: Your advice did solve the problem, thanks! I wonder which specific entry in the changelog did it... Great! I thought you might at least see some different behavior. There has been a fair bit of work done in th

Re: Madness with the 'select' function, sigalrm, and stdout. (CYGWIN_NT-6.1-WOW64)

On 1/17/2012 5:34 PM, Robert F wrote: This has me stumped. I'd suggest trying a snapshot - If that doesn't help, a full problem report might help someone on the list spot an issue. Problem reports: http://cygwin.com/problems.html I might give the

Re: Madness with the 'select' function, sigalrm, and stdout. (CYGWIN_NT-6.1-WOW64)

Larry Hall (Cygwin cygwin.com> writes: > Your advice did solve the problem, thanks! I wonder which specific entry in the changelog did it... The unwillignness to show any text until it finds a newline seems it could be a cygwin issue. Taking the following code: #ifndef __CYGWIN__ #define SLEE

Re: Madness with the 'select' function, sigalrm, and stdout. (CYGWIN_NT-6.1-WOW64)

Robert F hotmail.co.uk> writes: > > > > I might give the snapshot a shot. Do you know how far from the release > > build > > the latest snapshot is and when the next one is planned? > > > > Update: I did a flat replacement of cygwin1.dll with the latest snapshot of it > and all my cygwin ap

Re: Madness with the 'select' function, sigalrm, and stdout. (CYGWIN_NT-6.1-WOW64)

> I might give the snapshot a shot. Do you know how far from the release build > the latest snapshot is and when the next one is planned? > Update: I did a flat replacement of cygwin1.dll with the latest snapshot of it and all my cygwin apps go apesh*t. Is it because I didn't update the whole

Re: Madness with the 'select' function, sigalrm, and stdout. (CYGWIN_NT-6.1-WOW64)

> > This has me stumped. > > I'd suggest trying a snapshot - > > If that doesn't help, a full problem report might help someone on the list > spot an issue. > > > Problem reports: http://cygwin.com/problems.html > I might give the snapshot a shot. Do

Re: Madness with the 'select' function, sigalrm, and stdout. (CYGWIN_NT-6.1-WOW64)

On 1/17/2012 5:25 PM, Larry Hall (Cygwin) wrote: On 1/17/2012 5:16 PM, Robert F wrote: This could be a cygwin bug, but I'm not 100% sure. It may even be a weird interaction with the windows console. I have a single threaded app that loops, polls network activity with a 'select' function and int

Re: Madness with the 'select' function, sigalrm, and stdout. (CYGWIN_NT-6.1-WOW64)

On 1/17/2012 5:16 PM, Robert F wrote: This could be a cygwin bug, but I'm not 100% sure. It may even be a weird interaction with the windows console. I have a single threaded app that loops, polls network activity with a 'select' function and interrupts the flow of the loop when a SIGALRM signa

Madness with the 'select' function, sigalrm, and stdout. (CYGWIN_NT-6.1-WOW64)

This could be a cygwin bug, but I'm not 100% sure. It may even be a weird interaction with the windows console. I have a single threaded app that loops, polls network activity with a 'select' function and interrupts the flow of the loop when a SIGALRM signal is ran, the handler of which sets a va