From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24694 invoked by alias); 7 Dec 2001 00:04:32 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 24655 invoked from network); 7 Dec 2001 00:04:28 -0000 Received: from unknown (HELO cygnus.com) (205.180.230.5) by sources.redhat.com with SMTP; 7 Dec 2001 00:04:28 -0000 Received: from cse.cygnus.com (cse.cygnus.com [205.180.230.236]) by runyon.cygnus.com (8.8.7-cygnus/8.8.7) with ESMTP id QAA05800; Thu, 6 Dec 2001 16:04:25 -0800 (PST) Received: (from kev@localhost) by cse.cygnus.com (8.9.3/8.9.3) id RAA08746; Thu, 6 Dec 2001 17:03:57 -0700 Date: Thu, 06 Dec 2001 16:04:00 -0000 From: Kevin Buettner Message-Id: <1011207000357.ZM8745@ocotillo.lan> In-Reply-To: David Relson "Problem with threaded program" (Dec 2, 11:44am) References: <4.3.2.7.2.20011202114313.00c40ab0@mail.osagesoftware.com> X-Mailer: Z-Mail (4.0.1 13Jan97 Caldera) To: David Relson , gdb@sources.redhat.com Subject: Re: Problem with threaded program MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2001-12/txt/msg00071.txt.bz2 On Dec 2, 11:44am, David Relson wrote: > Here's the test program, test.c: > > #include > int main() { > char *t="1.0"; > double d=0; > d=strtod(t,(char **)NULL); > printf( "%f\n", d ); > return 0; > } > > Build using "gcc -g -lpthread test.c"; run using "gdb a.out". > > If you step through the program one line at a time and display variable d > after each assignment, the strtod() call seems to return > "nan(0x8000000000000)", which is also shown by print(). > > If you restart the program with a breakpoint at printf(), let it run, and > display d at the breakpoint, the value shown is "1.000000" which is correct. > > Is this a defect in gdb, or is my analysis wrong? It's a defect in gdb. I've just posted a patch which fixes this bug. See http://sources.redhat.com/ml/gdb-patches/2001-12/msg00183.html It hasn't been approved yet, but once it has, I'll push for getting it into 5.1.1 too. Thanks, Kevin