Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Date: Tue, 19 Nov 2002 11:53:45 -0500
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Emacs hangs again (1.3.15, 20021115 and 20021119(!) snapshots)
Message-ID: <20021119165345.GB18466@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <3DDA2A8D DOT 3000609 AT st DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3DDA2A8D.3000609@st.com>
User-Agent: Mutt/1.5.1i

On Tue, Nov 19, 2002 at 01:11:57PM +0100, Pavel Holejsovsky wrote:
>Hello,
>
>I'm experiencing yet another kind of hangs of emacs (running in X 
>window). This happens during emacs startup, but only if I resize its 
>window with mouse while emacs is processing startup files. Then it never 
>finishes its startup and eats 100% of CPU (quite similar symptoms of 
>previous bug fixed in 20021115 snapshot).
>
>I've verified the same behaviour with 1.3.15-2 cygwin1 release, 20021115 
>and 20021119 snapshots.
>
>strace shows this fragment, looping forever:
>
>   .... <repeat start here> ....
>
>   55 17683118 [main] emacs 2884 cygwin_select: 6, 0x1FB3FC, 0x0, 0x0, 0x0
>   56 17683174 [main] emacs 2884 dtable::select_read: /dev/streamsocket 
>fd 5
>   29 17683203 [main] emacs 2884 cygwin_select: to NULL, ms FFFFFFFF
>   30 17683233 [main] emacs 2884 cygwin_select: sel.always_ready 0
>   56 17683289 [main] emacs 2884 start_thread_socket: Handle 0x6F4
>   28 17683317 [main] emacs 2884 start_thread_socket: Added to readfds
>  135 17683452 [main] emacs 2884 start_thread_socket: exitsock 0x624
>   51 17683503 [main] emacs 2884 start_thread_socket: stuff_start 0x1FB2E0
>   58 17683561 [main] emacs 2884 select_stuff::wait: m 2, ms 4294967295
>   33 17683594 [main] emacs 2884 select_stuff::wait: signal received
>   80 17683674 [main] emacs 2884 select_stuff::cleanup: calling cleanup 
>routines
>   35 17683709 [main] emacs 2884 socket_cleanup: si 0x2051FA60 
>si->thread 0x610CA824
>   31 17683740 [main] emacs 2884 socket_cleanup: connection to 
>si->exitsock 0x624
>  315 17684055 [select_socket] emacs 2884 thread_socket: stuff_start 
>0x20522A84
>   55 17684110 [select_socket] emacs 2884 thread_socket: Win32 select 
>returned 2
>   35 17684145 [select_socket] emacs 2884 thread_socket: s 0x203B9590, 
>testing fd 5 (/dev/streamsocket)
>   33 17684178 [select_socket] emacs 2884 thread_socket: read_ready
>   30 17684208 [select_socket] emacs 2884 thread_socket: saw exitsock read
>  165 17684373 [main] emacs 2884 socket_cleanup: returning
>   32 17684405 [main] emacs 2884 select_stuff::~select_stuff: deleting 
>select records
>
>   .... <repeated forever> ....
>
>Unfortunately, I'm not able to say from this whether is it a bug in 
>cygwin's select() internals or emacs calling it forever for some other 
>strange reason. I'll try to understand cygwin's select.cc code and 
>analyze further, but in the meanwhile, if anyone has any idea..
>
>I've the full strace output, but it is quite big (800kB bz2). If anyone 
>wants it, I can post it privately.

Unless you are actually familiar with cygwin internals, posting strace
logs or even strace snippets is probably worthless in the majority of
the cases.  There is nothing in the above code which indicates that
anything is wrong.

It would really be wonderful to have someone actually debugging this
problem rather than speculating on what they think might be wrong and
sending YA snippet of normal strace logs to the list.

Ah.  I can dream, can't I?

cgf

--
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/