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 3530 [details]
Xamarin Studio 2.0
Hover over ds variable after this line is executed:
DataSet ds = new DataSet();
The value tooltip will show "Evaluation failed: System.NullReferenceException" instead of normal object tooltip.
Do you have a small test case so that I can reproduce this?
I'm not able to reproduce this with a small test program that just has the above line (and a Console.WriteLine() right after it).
That's enough code for me - just create a DataSet instance and inspect the variable.
Note that I am running Xamarin Studio on Windows x64 (7 and 8) without mono framework.
I've also attached a debugger and stopped on that exception.
Message=Evaluation failed: System.NullReferenceException
at MonoDevelop.Debugger.Win32.CorDebuggerSession.RuntimeInvoke(CorEvaluationContext ctx, CorFunction function, CorType typeArgs, CorValue thisObj, CorValue arguments)
Ah, that explains it: I've been testing with the Mono backend on Mac.
The CorDebugger backend is really really really broken. If you can, I suggest debugging with the Mono backend instead.
So, does it make sense to bother with CorDebugger bugs at all?
You mean submitting them? I don't mind if you find/submit more CorDebugger bugs as it would be good to keep track of them so that either we or a contributor can fix them.
This issue has been fixed and will be included in future releases.
I have verified this issue and not getting "Evaluation failed: System.NullReferenceException". following are the steps:
1. Created a sample iOS project.
2. Added below code:
DataSet ds = new DataSet()
String str = ds.DataSetName
3. apply beak point at "Console.WriteLine(str)" line
4. Debug application.
Refer Screen shot: http://screencast.com/t/vIuM8zDkWXo3
XS 4.2.3 (build 24)
Also I have verified on machine with following steps:
1. Created console application.
2. Added above my comment code.
3. Apply break point
4. Debug application and not getting issue.
Refer screen shot: http://screencast.com/t/f66jk44FTtaS
XS 4.2.3 (build 23)