Bug 4931 - Debugger cannot Evaluate TaskStatus variables
Summary: Debugger cannot Evaluate TaskStatus variables
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Debugger ()
Version: 2.9.x
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Jeffrey Stedfast
: 5135 5168 ()
Depends on:
Reported: 2012-05-07 16:25 UTC by Eric Beisecker
Modified: 2012-05-21 12:00 UTC (History)
3 users (show)

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

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 Eric Beisecker 2012-05-07 16:25:03 UTC
When debugging an application in MonoDevelop the debugger returns an error as the value for variables of the 'TaskStatus' type.

Screencast: http://screencast.com/t/8OUoi0VwKlIa
Comment 1 Mikayla Hutchinson [MSFT] 2012-05-07 18:20:55 UTC
It also looks like it stopped displaying breakpoint and execution markers correctly...

What MD revision is this?
Comment 2 Eric Beisecker 2012-05-07 18:23:01 UTC
5830190996715c87a5421a5a16559e1e717bd3a7 From Wrench.
Comment 3 Mikayla Hutchinson [MSFT] 2012-05-07 18:31:30 UTC
Looks like we need to backport https://github.com/mono/monodevelop/commit/7732dee78858f6db9ab1b27656aa1e028e6d7fec for the marker rendering issue.

Dunno about the .ctor issue, maybe we need to backport more of Jeff's evaluator fixes.
Comment 4 Jeffrey Stedfast 2012-05-11 15:10:58 UTC
I'm not able to reproduce the Int64 ctor issue in master (and I don't think there are any debugger bugs that I haven't backported to 3.0-series)
Comment 5 Jeffrey Stedfast 2012-05-16 13:44:54 UTC
Fixed in git master and 3.0-series
Comment 6 Jeffrey Stedfast 2012-05-17 12:55:27 UTC
*** Bug 5135 has been marked as a duplicate of this bug. ***
Comment 7 Jeffrey Stedfast 2012-05-18 12:05:43 UTC
*** Bug 5168 has been marked as a duplicate of this bug. ***
Comment 8 Jeffrey Stedfast 2012-05-18 16:15:50 UTC
just hit this a second ago, apparently not fixed
Comment 9 Jeffrey Stedfast 2012-05-21 12:00:33 UTC
I think I must have been using 3.0 at the time and not git master