I’m testing FPU with double variables on Cortex A7. The local window shows correct values but the tooltip over the variable shows wrong data. See picture.
Could you please try evaluating the variable via the GDB Session window (“print <variable name>”)? Does this show correct values?
Perhaps the variable name is confused with something else, like a global variable with the same name of a register? Does the Watch window show correct value?
you are right. It depends on the name and it was a conflict with an ARM NEON register name (d2).
double d2 = 1.125;
double dV2 = 1.125;
d2 shows wrong value (interpreted as builtin_type_ieee_double), dV2 ist correct (interpreted as double).
This reply was modified 8 years, 6 months ago by WalterF.
That’s a known issue. VisualGDB automatically substitutes register names to support data tooltips for inline assembly. As a workaround please use the Locals window or rename your variables.