Actions
| Post | |
| Subscribe | |
| Unsubscribe |
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [arm-gnu] doubles display way off in gdb/insight
- To: "Gene Smith" <gds@xxxxxxxxxxxxx>, <arm-gnu@xxxxxxxxxxxxxxxx>
- Subject: RE: [arm-gnu] doubles display way off in gdb/insight
- From: "James Kehl" <jamesk@xxxxxxxxxxx>
- Date: Tue, 9 Feb 2010 11:06:31 +1000
> -----Original Message----- > From: Gene Smith [mailto:gds@xxxxxxxxxxxxx] > Sent: Sunday, 7 February 2010 9:30 AM > To: arm-gnu@xxxxxxxxxxxxxxxx > Subject: [arm-gnu] doubles display way off in gdb/insight > > In my program doubles work fine. But when I inspect them in gdb (or > insight) they appear wildly off: example: 3.14e0 => 943.3e315. Plain > floats are OK. This is with cortex m3. Doubles display fine when > debugging with insight with native x86 programs. Anyone else see this > and, if so, know a solution? > There can be lots of hassles with ARM doubles and endianness - depending on the architecture and ABI, they can be big-, little- or even middle-endian. This wouldn't turn 3.14e0 into 943.3e315, though - 943.3e315 is actually larger than DBL_MAX, so I don't know where that could have come from. Was that the exact number? Does 0.0 map to 0.0? J
- References:
- [arm-gnu] doubles display way off in gdb/insight
- From: Gene Smith
- [arm-gnu] doubles display way off in gdb/insight
- Prev by Date: [arm-gnu] Compiling Safety Related Systems?
- Next by Date: Re: [arm-gnu] Compiling Safety Related Systems?
- Previous by thread: Re: [arm-gnu] doubles display way off in gdb/insight
- Next by thread: [arm-gnu] Compiling Safety Related Systems?
- Index(es):