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] |
On Dec 2 14:56, Jon TURNEY wrote: > On 02/12/2013 14:17, Corinna Vinschen wrote: > > On Dec 2 13:11, Jon TURNEY wrote: > >> What you write does seem to support the theory that this is a regression in > >> select() in the cygwin DLL. It might be useful if you could say what version > >> of the cygwin DLL you had when it was working correctly before you upgraded. > >> > >> [1] http://cygwin.com/ml/cygwin-xfree/2013-10/msg00031.html > >> [2] http://cygwin.com/ml/cygwin-xfree/2013-11/msg00012.html > > > > Are you sure this is a select problem? If so, can you create an STC, > > perhaps? > > "Only a madman is absolutely sure". I'm afraid the best test case I have a > the moment is: > > Install xorg-server-debuginfo > Start XWin -noclipboard -multiwindow > Start xwinclip under gdb, and place a breakpoint at wndproc.c:133, and run it > Start emacs-x11, open the Shakespeare text from [1] in a buffer > Open notepad > Copy and paste the text from the emacs buffer into notepad > The breakpoint is hit. Notice that select() has returned 0, the read ready > fd_set is empty and the timeout hasn't expired. I claim that the read ready > fd_set should indicate that the X connection socket is ready. Well, that's not exactly an STC... So, IIUC, you're saying that, in fact, select doesn't return too early, rather it returns without setting the return value correctly. You expect it to return a value > 0, right? Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat
Attachment:
pgppTu3lFSgUs.pgp
Description: PGP signature
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |