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