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: Wed, 18 Feb 2004 10:57:42 -0500 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: 20040217 snapshot problem Message-ID: <20040218155742.GA3470@redhat.com> Mail-Followup-To: cygwin@cygwin.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i X-IsSubscribed: yes Reply-To: cygwin@cygwin.com On Wed, Feb 18, 2004 at 10:51:56AM -0500, Richard Campbell wrote: >I was trying the 20040217 snapshot to see if it cleared up the emacs >problems I was having (which haven't been repeatable enough for me to >report). After installing the 20040217 snapshot, starting X led to >inetd consuming all available cpu and no X starting. After shutting >down inetd, starting X just returned. XWin.exe dropped straight back >to a command prompt. > >This is repeatable - I've switched cygwin1.dll back and forth from >1.5.7-1 to 20040217 snapshot, and XWin.exe works or doesn't based on >the dll. > >Cygcheck output attached. > >How best to track this down a little better? Is this a regression from 20040216 or some other snapshot? -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/