Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Date: Sat, 28 Apr 2001 00:33:26 -0400 From: Christopher Faylor To: "'cygwin@cygwin.com'" Subject: Re: cygwin 1.3.1 bug in fscanf("%lf", &a) Message-ID: <20010428003326.B12841@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: "'cygwin@cygwin.com'" References: <03781128C7B74B4DBC27C55859C9D738D4296E@es06snlnt> <3AE9ED59.7D8C51D6@ece.gatech.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <3AE9ED59.7D8C51D6@ece.gatech.edu>; from cwilson@ece.gatech.edu on Fri, Apr 27, 2001 at 06:06:17PM -0400 On Fri, Apr 27, 2001 at 06:06:17PM -0400, Charles S. Wilson wrote: >This is probably related to the ongoing thread "bug report: sscanf >problem with cygwin 1.3.1-1". All *scanf() functions will have a >similar bug. Me, I'm still waiting on the build of my debuggable kernel >to finish (us poor grad students don't own fast computers....) Has >anybody had a chance to debug the __svfscanf_r() routine? I haven't debugged it. Maybe I should submit another bug report with a different subject. How about Subject: What gives with scanf in cygwin 1.31? That has a nice ring to it and I'm sure that the repetition will serve to motivate someone. cgf -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple