Bug 1258 - [2.8] Debugger window doesn't support boxing of primitive types
Summary: [2.8] Debugger window doesn't support boxing of primitive types
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Debugger ()
Version: 2.8
Hardware: PC Windows
: Low minor
Target Milestone: master
Assignee: Bugzilla
Depends on:
Reported: 2011-10-05 13:44 UTC by Mike Christensen
Modified: 2015-08-20 03:24 UTC (History)
4 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 Mike Christensen 2011-10-05 13:44:47 UTC

Run the following code in the Immediate window (I just created a Console app, but probably doesn't matter)

> 123.ToString();
Evaluation failed.

It seems "123" isn't boxed to an Int32, which has a ToString() method.  This works fine under Visual Studio.


Ideally, statement should be evaluated.  If there is a limitation of the soft debugger, a better error message should be displayed.

Note: Running on 2.8 release under Windows XP, but there's no "2.8" option in the Version dropdown yet.  Please update bug when this happens.
Comment 1 Jeffrey Stedfast 2011-12-02 16:46:22 UTC
Drilling down into "ValidationResult vres = ff.ValidateExpression (tt, ops);" from ImmediatePad.cs, looks like NRefactoryEvaluator might need to be modified.

Looks like it is currently using the OldNRefactory expression parser, so this probably depends on the newresolver branch.

Mike: have you ported this code to the new resolver in your branch yet? And would that fix this?
Comment 2 Jeffrey Stedfast 2012-04-19 17:24:31 UTC
Looking into this again... I was wrong before. This isn't an issue with the resolver, it's an issue with the SoftDebugger backend that invokes methods on primitive values (which wasn't supported).

I've fixed this in git master (might make it into MonoDevelop 3.0)