This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: SIGTSTP and select


On Thu, Apr 05, 2007 at 07:31:39PM -0400, Bob Rossi wrote:
> On Tue, Apr 03, 2007 at 10:42:39AM -0400, Bob Rossi wrote:
> > On Tue, Apr 03, 2007 at 10:13:20AM -0400, Bob Rossi wrote:
> > > On Mon, Apr 02, 2007 at 08:37:53PM -0400, Christopher Faylor wrote:
> > > > On Mon, Apr 02, 2007 at 08:07:23PM -0400, Bob Rossi wrote:
> > > > >So, my question is, is there a bug with select on cygwin? Is select
> > > > >working properly and I should handle the read call differently? Why does
> > > > >it act differently than linux?
> > > > 
> > > > You say that something changed between different releases but you don't
> > > > mention what those releases are.  Is this releases of Cygwin?  If so,
> > > > what releases?
> > > > 
> > > > If this is as easy to demonstrate as you say, then a simple test case
> > > > is definitely called for.
> > > 
> > > Hi Christopher,
> > > 
> > > Attached is the test case. If I run it under linux, and then type ctrl-z, I 
> > > never get into the user_input_loop call. If I run it in cygwin, I do.
> > > 
> > > Hopefully I'm doing something wrong here. Please advise!
> > 
> > Ouch. Attached.
> 
> Any idea if this is a bug in cygwin?
> 
> I'm considering if I should rework my code to handle this case...

Ping. Just wondering what actions I should take. I would very much like
to get a release of cgdb out this week.

Bob Rossi

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]