Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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
Message-ID: <415E1E99.A9140A6D@dessent.net>
Date: Fri, 01 Oct 2004 20:20:57 -0700
From: Brian Dessent <brian AT dessent DOT net>
Organization: My own little world...
MIME-Version: 1.0
To: Ben Wing <ben AT 666 DOT com>
CC: cygwin AT cygwin DOT com
Subject: Re: Scanf bug
References: <003201c4a83c$f6fd3530$210110ac AT NEEEEEEE>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Reply-To: cygwin AT cygwin DOT com

Ben Wing wrote:
> 
> Somehow or other, sscanf() has gotten messed up in recent Cygwin
> installations.

I believe this probably belongs on the newlib list, since Cygwin uses
newlib for libc.

That said, it looks like the following could be your culpret... Or at
least, it's the only scanf-related newlib commit that I can find in the
last 6 months that seems to be applicable.

http://cygwin.com/ml/newlib-cvs/2004-q2/msg00034.html

Brian

--
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/