X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Mon, 17 Mar 2008 16:46:20 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: please help: crash on vista Message-ID: <20080317154620.GB16519@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <7c5010d60803170346v638ab1e5k37134c0a35aacc1f AT mail DOT gmail DOT com> <7c5010d60803170724w585d8010o581b821ce4a9ad63 AT mail DOT gmail DOT com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <7c5010d60803170724w585d8010o581b821ce4a9ad63@mail.gmail.com> User-Agent: Mutt/1.5.16 (2007-06-09) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 On Mar 17 15:24, Giovanni Maruzzelli wrote: > Dear Corinna, dear Cygwin developers, > > I've run both the sample case and my program with the cygwin1.dll > snapshot from 2008-03-02 (cygwin1-20080302.dll.bz2) and they works > fine (actually, much better than with previous version of cygwin). > > So, it seems that the problem related to my crashes was introduced > between the last snapshot and the 1.5.25, that was released couple > days after that snapshot. > > There is a changelog between that snapshot and the release? The snapshots and Cygwin 1.5.25 are not using the same code. To fetch the code of 1.5.25, use the sources provided through setup.exe, or check out the sources from the CVS(*) branch 'cr-0x5f1'. Corinna (*) http://cygwin.com/cvs.html -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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/