From: David Relson <relson@osagesoftware.com>
To: gdb@sources.redhat.com
Subject: Problem with threaded program
Date: Sun, 02 Dec 2001 08:44:00 -0000 [thread overview]
Message-ID: <4.3.2.7.2.20011202114313.00c40ab0@mail.osagesoftware.com> (raw)
Greetings,
The problem below was originally reported to the Linux Kernel Mailing
List. It looks to me to be a gdb problem.
I used a freshly compiled and installed copy of gdb-5.1 (configured as
"i686-pc-linux-gnu") for this test on a Pentium III 500mhz running the
2.4.16 kernel. The same problem happens with gdb-5.0. gdb-4.18 appears to
work fine.
Here's the test program, test.c:
#include <stdlib.h>
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?
David
P.S.
--------------------------------------------------------
David Relson Osage Software Systems, Inc.
relson@osagesoftware.com Ann Arbor, MI 48103
www.osagesoftware.com tel: 734.821.8800
next reply other threads:[~2001-12-02 16:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <David Relson <relson@osagesoftware.com>
2001-12-02 8:44 ` David Relson [this message]
2001-12-02 10:41 ` Andrew Cagney
2001-12-02 15:48 ` Daniel Jacobowitz
2001-12-02 17:24 ` David Relson
2001-12-02 21:28 ` Andrew Cagney
2001-12-03 4:14 ` David Relson
2001-12-03 7:49 ` Trond Eivind Glomsrød
2001-12-06 16:04 ` Kevin Buettner
2001-12-06 16:37 ` David Relson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4.3.2.7.2.20011202114313.00c40ab0@mail.osagesoftware.com \
--to=relson@osagesoftware.com \
--cc=gdb@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox