Bug 8511 - Expression Evaluator Evil Voodoo Magic
Summary: Expression Evaluator Evil Voodoo Magic
Status: RESOLVED DUPLICATE of bug 8779
Alias: None
Product: Android
Classification: Xamarin
Component: Debugger ()
Version: 4.2.x
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2012-11-19 16:45 UTC by Yvan Rodrigues
Modified: 2012-12-08 00:27 UTC (History)
4 users (show)

Is this bug a regression?: ---
Last known good build:

Voodoo screenshot (175.63 KB, image/png)
2012-11-19 16:45 UTC, Yvan Rodrigues
Sample project (513.04 KB, application/x-zip-compressed)
2012-11-19 16:57 UTC, Yvan Rodrigues

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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.

Related Links:

Description Yvan Rodrigues 2012-11-19 16:45:31 UTC
Created attachment 2970 [details]
Voodoo screenshot

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.
Comment 1 Yvan Rodrigues 2012-11-19 16:57:56 UTC
Created attachment 2971 [details]
Sample project

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.
Comment 2 Jeffrey Stedfast 2012-11-19 17:47:04 UTC
Zoltan: didn't you already fix this? Does M4A just need to update its Mono runtime?
Comment 3 Zoltan Varga 2012-11-19 21:54:57 UTC
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.
Comment 4 Jonathan Pryor 2012-12-08 00:27:40 UTC
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 ***