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: Fri, 21 Jan 2005 14:02:33 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: cygwin bughunt (FAQ alert?) Message-ID: <20050121190233.GD20866@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com References: <20050121121553 DOT GQ3113 AT cygbert DOT vinschen DOT de> <20050121163843 DOT GE20002 AT trixie DOT casa DOT cgf DOT cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i On Fri, Jan 21, 2005 at 11:53:25AM -0500, Igor Pechtchanski wrote: >Also agreed. But the source provided in the cygwin source package is >worthless for debugging, since one can't build Cygwin from that source. >If debugger symbols were available, that source would actually be >useful. :-) Huh? tar xjf cygwin-1.5.12-1-src.tar.bz2 cd cygwin-1.5.12-1 mkdir build cd build (../configure; make) >& make.out This builds a cygwin DLL. Just tried it. Since all of your arguments were presupposing something to do with CVS, I assume that this addresses your concerns. You don't need CVS and I did not say that you had to use CVS. It does make sense to check CVS or a snapshot to see if your problem is fixed before you go to any effort trying to debug a problem, however. 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/