On Sun, Dec 04, 2011 at 08:03:18PM -0600, Yaakov (Cygwin/X) wrote: >On Sun, 2011-12-04 at 14:27 -0500, Christopher Faylor wrote: >> The real problem seemed to be a change introduced after 1.7.9 which >> subtly broke the handling of signals during I/O. That should be fixed >> in the latest snapshot but, like so much of what I've worked on in Cygwin >> lately, it touched a fundamental part of the code. I wish I hadn't had >> to make this change just before 1.7.10 but, in theory, it should make >> it possible for a signal handler to be caught in a thread - that's a first >> for Cygwin and it's something I've been meaning to get to for a while. > >The 20111204 snapshot fixes gnome-keyring. Thanks!
That's a relief. I have to admit that this is one of the few times that I fixed a problem without first understanding the root cause. I saw that there was something fishy going on but it didn't seem to relate to the gnome-keyring problem. But after several stabs at fixing the fishy problem, the gnome-keyring problem vanished. >> This isn't perfect though and I hope that doesn't mean that I've >> introduced other corner case problems. > >I'll continue testing CVS HEAD and see what happens. How much more >churn are you planning before 1.7.10? I think (unless Corinna disagrees) that the current snapshot should be considered 1.7.10rc1. I really don't want to perturb the source code any more now unless it's absolutely necessary. Even this current fix is basically just a band-aid. I hope to rework some of the signal handling for 1.7.11 to make things a little less ugly. cgf -- 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
