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: Mon, 29 Nov 2004 22:32:09 -0500 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: A vexing installation problem Message-ID: <20041130033209.GB1015@trixie.casa.cgf.cx> Reply-To: cygwin@cygwin.com References: <20041129184442.GA30302@sonic.net> <6.2.0.14.0.20041129135305.046bca10@pop.prospeed.net> <20041129195946.GA4932@sonic.net> <6.2.0.14.0.20041129151309.046bfba0@pop.prospeed.net> <20041129215220.GA15085@sonic.net> <6.2.0.14.0.20041129171109.046d1728@pop.prospeed.net> <20041129231740.GA32760@sonic.net> <6.2.0.14.0.20041129181904.046bf960@pop.prospeed.net> <20041130011421.GA20359@sonic.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/