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 From: "Gary R. Van Sickle" To: Subject: RE: Heads up: *possible* bug in cygwin Date: Fri, 3 Jan 2003 00:25:50 -0600 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal In-Reply-To: <20030102192138.GA1668@tishler.net> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Importance: Normal > Chuck, > > On Wed, Jan 01, 2003 at 11:36:49PM -0500, Charles Wilson wrote: > > Turns out, the problem IS in newlib. > > I concur. In fact, this problem is the root cause for the Cygwin Python > SEGV that I was trying to debug in the following: > > http://cygwin.com/ml/cygwin-developers/2002-12/msg00027.html > > For those interested, Python's test_format regression test would SEGV > after trying to display a 109 digit number. Unfortunately, this > occurred deep in Python's garbage collection during exit which threw me > off the track. Sigh... > > Thanks for your astute analysis. With the attached "patch," I was able > to get test_format to pass. I will monitor the newlib list to see what > the outcome is. > > Jason > Free software is so very, very sweet. Thanks to everybody involved in killing this latent (to me anyway) defect. -- Gary R. Van Sickle Brewer. Patriot. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/