Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Thu, 14 Nov 2002 18:50:04 +0000 Message-ID: <3659-Thu14Nov2002185004+0000-starksb@ebi.ac.uk> From: David Starks-Browning MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: cygwin@cygwin.com Subject: Re: patched cygwin emacs available (for signal looping problem) In-Reply-To: <20021114184111.GB15314@redhat.com> References: <20021114172850.GB1550@redhat.com> <4515-Thu14Nov2002182404+0000-starksb@ebi.ac.uk> <20021114184111.GB15314@redhat.com> On Thursday 14 Nov 02, Christopher Faylor writes: > >> There is a new cygwin snapshot which *may* fix this behavior, too. > >> Please try it. > > > >No, I tried it, it does not help. > > Well, that's wonderful. One report of "It works, sort of" and one of > "It doesn't fix the problem 100%". Not sure what Pavel meant by "sort of". I find that Emacs will start spinning at various places. Maybe how long it takes to trip up, depends on what version of emacs.exe and/or cygwin1.dll. I even failed to get it to spin once. When it spins, attach with strace and you see the signal loop that we've been reporting recently. Maybe Pavel could get it to "sort of work" (not work, but also not consume 100% cpu?) and attach with strace to confirm the symptoms. Regards, David -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/