Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Wed, 8 Dec 2004 11:22:16 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: 1.5.12: problems without registry keys Message-ID: <20041208162216.GH1735@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT 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 On Wed, Dec 08, 2004 at 04:08:28PM -0000, Dave Korn wrote: >I'm running with a fairly recent CVS build of cygwin. Maybe there was >a problem at some point that is now fixed, in which case a snapshot >should fix it. I'm not aware of any problems in this regard. The registry code in CVS is more robust these days thanks (as usual) to Pierre Humblet but prior to that the code hasn't changed much in months. I'd suspect cockpit errors myself. I don't see any reason why cygwin would hang if registry keys are missing. It would be worth trying the latest snapshot and debugging with gdb, however. The latest snapshot has debugging symbols. Don't use it for anything more than debugging however. It has some problems with starting/stopping processes. cgf -- 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/