Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
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" <g DOT r DOT vansickle AT worldnet DOT att DOT net>
To:	<cygwin AT cygwin DOT com>
Subject:	RE: Heads up: *possible* bug in cygwin
Date:	Fri, 3 Jan 2003 00:25:50 -0600
Message-ID:	<NCBBIHCHBLCMLBLOBONKMEEGDKAA.g.r.vansickle@worldnet.att.net>
MIME-Version:	1.0
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/

- Raw text -