X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.1 required=5.0 tests=AWL,BAYES_00,FAKE_REPLY_C,SPF_PASS X-Spam-Check-By: sourceware.org Content-Type: text/plain; charset="us-ascii" Date: Sun, 29 Nov 2009 14:54:03 +0100 From: =?iso-8859-1?Q?=22Torsten_Sch=FCtze=22?= Message-ID: <20091129135403.243590@gmx.net> MIME-Version: 1.0 Subject: Re: [ANNOUNCEMENT] [1.7] Updated: cygwin-1.7.0-67 To: cygwin AT cygwin DOT com Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 Hi, Corinna Vinschen wrote: > - Fix a potential stack corruption in stat() which only occurs > on filesystems not supporting security (FAT, FAT32). See > http://cygwin.com/ml/cygwin/2009-11/msg00881.html it seems to me that the recent patch in stat() for 1.7.0-67 actually fixed the problem reported by me in http://cygwin.com/ml/cygwin/2009-09/msg00010.html We couldn't debug this bug successfully at that time, but it occurred only by diffing on a FAT32 formatted USB stick (with Truecrypt encryption) and is now gone. With all the previous versions up to 1.7.0-66 the buggy behaviour was still there. So at least for me Cygwin 1.7.0-67 is ready for the 1.7.1 release. Great work! Thanks a lot Torsten -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple