public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "sogartary at yahoo dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/15318] New: Printing floating point numbers as hexadecimal outputs wrongly the integer conversion Date: Thu, 28 Mar 2013 12:31:00 -0000 [thread overview] Message-ID: <bug-15318-4717@http.sourceware.org/bugzilla/> (raw) http://sourceware.org/bugzilla/show_bug.cgi?id=15318 Bug #: 15318 Summary: Printing floating point numbers as hexadecimal outputs wrongly the integer conversion Product: gdb Version: 7.5 Status: NEW Severity: normal Priority: P2 Component: gdb AssignedTo: unassigned@sourceware.org ReportedBy: sogartary@yahoo.com Classification: Unclassified When printing a float or a double as a hexadecimal the number is first cast to integer and then the integer is printed in hex. The correct behaviour is to take the bits of the floating point value, reinterpret them as integer and print them in hex. Here is an example. We have the following code: double dd = 0.00014335116245 + 0x1FFF; then in GDB after breaking on the next line we issue the following commands: (gdb) p dd $1 = 8191.0001433511625 (gdb) p/x 8191 $2 = 0x1fff (gdb) p/x dd $3 = 0x1fff (gdb) p/x *reinterpret_cast<int64_t*>(&dd) $4 = 0x40bfff000965088e On the third command GDB should return the same as the result from the fourth command. -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next reply other threads:[~2013-03-28 12:31 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-03-28 12:31 sogartary at yahoo dot com [this message] 2013-03-28 12:32 ` [Bug gdb/15318] " sogartary at yahoo dot com 2013-03-28 12:35 ` sogartary at yahoo dot com 2013-03-28 12:41 ` [Bug c++/15318] " sogartary at yahoo dot com 2013-03-28 16:07 ` tromey at redhat dot com 2013-04-05 15:49 ` sogartary at yahoo dot com 2020-06-06 14:59 ` tromey at sourceware dot org
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=bug-15318-4717@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.org \ /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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).