From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14953 invoked by alias); 21 Jan 2005 19:02:44 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 14790 invoked from network); 21 Jan 2005 19:02:25 -0000 Received: from unknown (HELO cgf.cx) (66.30.17.189) by sourceware.org with SMTP; 21 Jan 2005 19:02:25 -0000 Received: by cgf.cx (Postfix, from userid 201) id 3711F1B522; Fri, 21 Jan 2005 14:02:33 -0500 (EST) Date: Fri, 21 Jan 2005 19:26:00 -0000 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: cygwin bughunt (FAQ alert?) Message-ID: <20050121190233.GD20866@trixie.casa.cgf.cx> Reply-To: cygwin@cygwin.com References: <20050121121553.GQ3113@cygbert.vinschen.de> <20050121163843.GE20002@trixie.casa.cgf.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i X-SW-Source: 2005-01/txt/msg01051.txt.bz2 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/