From owner-freebsd-current Fri May 24 10:17:31 2002 Delivered-To: freebsd-current@freebsd.org Received: from espresso.q9media.com (espresso.q9media.com [216.254.138.122]) by hub.freebsd.org (Postfix) with ESMTP id 64B2A37B406 for ; Fri, 24 May 2002 10:17:28 -0700 (PDT) Received: (from mike@localhost) by espresso.q9media.com (8.11.6/8.11.6) id g4OHFo784135; Fri, 24 May 2002 13:15:50 -0400 (EDT) (envelope-from mike) Date: Fri, 24 May 2002 13:15:50 -0400 From: Mike Barcroft To: Chris Hedley Cc: freebsd-current@freebsd.org Subject: Re: strtod & sscanf on -CURRENT? Message-ID: <20020524131550.C26122@espresso.q9media.com> References: <20020524133357.GA15486@sysadm.stc> <20020524161853.U2404-100000@teabag.cbhnet> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020524161853.U2404-100000@teabag.cbhnet>; from cbh@teabag.demon.co.uk on Fri, May 24, 2002 at 04:24:04PM +0100 Organization: The FreeBSD Project Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Chris Hedley writes: > On Fri, 24 May 2002, Igor Roboul wrote: > > Maybe I'm wrong, but I think that sscanf on -CURRENT does not work as > > expected. > > Interestingly I had some aggro with both scanf and strtod returning > somewhat random results recently (about 5th/6th May); I'm afraid I no > longer have the results or test programs but I ended up having to hack my > own routine together to get a reliable input. What I seem to recall is > that scanf didn't return the correct result at all, whereas strtod was > okay for the first couple of invocations within the same program, after > which it began to return garbage (I'm pretty confident that my program > didn't have a buffer overrun, it was a fairly short & simple effort) Would it be possible for you to reproduce the source to a small program that demonstrates the problem? Best regards, Mike Barcroft To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message