Bug 36950 - [CorDebugger] Impossible to inspect the object if one of the properties throws an exception
Summary: [CorDebugger] Impossible to inspect the object if one of the properties throw...
Status: CONFIRMED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Debugger (show other bugs)
Version: 5.10 (C6SR3)
Hardware: PC Windows
: Low normal
Target Milestone: master
Assignee: David Karlaš
URL:
Depends on:
Blocks:
 
Reported: 2015-12-13 19:56 UTC by bluedzins
Modified: 2017-09-06 09:13 UTC (History)
2 users (show)

Tags:
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 for Bug 36950 on Developer Community or GitHub if you have new information to add and do not yet see a matching new report.

If the latest results still closely match this report, you can use the original description:

  • Export the original title and description: Developer Community HTML or GitHub Markdown
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:
Status:
CONFIRMED

Description bluedzins 2015-12-13 19:56:09 UTC
Plain C# console application with not null object. Say you set a breakpoint at some point and you would like to inspect that object -- by unfolding its properties in the object popup.

In Visual Studio (2010) you would see a list of its properties and fields, and the value of given member. If the member throws an exception, there is such message __for this member__.

In XS however if exception is thrown for any of the members, there is such message, but for entire object. Meaning you don't see a list of the members, and you don't know which member threw an exception. Minor thing is, the message currently is phrased in such way one could be mislead that the object itself threw an exception (like having null reference).