Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
Developer Community or GitHub with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
Created attachment 2970 [details]
I have a Coordinate class that contains a Latitude and Longitide as double properties.
Please see the screenshot.
In the first attachment I am inspecting an instance of the class. You can make some interesting observations.
- I know for a fact that LatitideDecimal~=43.55
- The Watch confirms this (the watch is set to "value.LatitudeDecimal"
- The EE is showing LatitudeDecimal==-4214944056E-07 (a very small number)
- When the EE executes value.ToString() you can see it shows teh value as a very large number.
It appears that the in-memory instance of the values contained in the class is corrupt.
Created attachment 2971 [details]
So this is interesting. Here is a project that replicates the problem.
When debugged in the emulator, the correct values are shown.
When debugged on a physical device, it shows the crazy values.
Zoltan: didn't you already fix this? Does M4A just need to update its Mono runtime?
There were problems with floaring point values in the debugger, those were fixed in c91fc1d6b68994c0c179c4ad99f1a656b14c61ec on mobile master. I don't know which m4a versions include that fix.
Looks like a dup of Bug #8779. Please try using the 4.4.x release.
*** This bug has been marked as a duplicate of bug 8779 ***