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: Mon, 29 Nov 2004 22:32:09 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: A vexing installation problem Message-ID: <20041130033209.GB1015@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com References: <20041129184442 DOT GA30302 AT sonic DOT net> <6 DOT 2 DOT 0 DOT 14 DOT 0 DOT 20041129135305 DOT 046bca10 AT pop DOT prospeed DOT net> <20041129195946 DOT GA4932 AT sonic DOT net> <6 DOT 2 DOT 0 DOT 14 DOT 0 DOT 20041129151309 DOT 046bfba0 AT pop DOT prospeed DOT net> <20041129215220 DOT GA15085 AT sonic DOT net> <6 DOT 2 DOT 0 DOT 14 DOT 0 DOT 20041129171109 DOT 046d1728 AT pop DOT prospeed DOT net> <20041129231740 DOT GA32760 AT sonic DOT net> <6 DOT 2 DOT 0 DOT 14 DOT 0 DOT 20041129181904 DOT 046bf960 AT pop DOT prospeed DOT net> <20041130011421 DOT GA20359 AT sonic DOT net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i On Mon, Nov 29, 2004 at 08:25:21PM -0500, Igor Pechtchanski wrote: >This suggests some sort of a problem with the Cygwin DLL initialization >code -- something that's very hard to debug. Try looking at the CVS >history for the Cygwin initialization code between the 1.5.5 and 1.5.6 >releases. Cygwin initialization code isn't particularly hard to debug. You just set breakpoints and debug it like any other part of cygwin. It's actually easier to debug than most other pieces because there aren't multiple threads running. 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/