On 10/22/2011 5:55 AM, Ken Brown wrote:
I'm wrong. I've been focusing too much on the select interruption. This is actually harmless and is correctly treated by emacs the same as a select timeout. It doesn't explain or solve the original gdb problem. Sorry for the noise.
I was finally able to make a testcase, showing that the problem I mentioned in the first post of this thread has nothing to do with emacs or select. It's a Cygwin/gdb problem. I've reported it in
http://cygwin.com/ml/cygwin/2011-10/msg00445.html Ken -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
