Bug 3473 - Invalid watch
Summary: Invalid watch
Status: RESOLVED FIXED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Debugger ()
Version: Trunk
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Jeffrey Stedfast
URL:
Depends on:
Blocks:
 
Reported: 2012-02-15 11:06 UTC by Sebastien Pouliot
Modified: 2012-02-16 16:23 UTC (History)
1 user (show)

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


Attachments
an image is worth a 1000 words :) (73.38 KB, image/png)
2012-02-15 11:06 UTC, Sebastien Pouliot
Details


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:
Status:
RESOLVED FIXED

Description Sebastien Pouliot 2012-02-15 11:06:14 UTC
Created attachment 1362 [details]
an image is worth a 1000 words :)

I tried MD master to get the fix for #3148. Now it "works" (no resolution error) but the watches values are not always correct.

It's likely a (missing) UI update issue because even the watch itself knows it's not ok, i.e. it can display details of a `null` instance. See attached screenshot.

Note: as the code shows the static property is not null (it just passed the Assert.NotNull call).
Comment 1 Jeffrey Stedfast 2012-02-16 15:56:17 UTC
I've just committed a patch which I think fixes this, but I'm not sure how to repro
Comment 2 Jeffrey Stedfast 2012-02-16 16:23:39 UTC
verified fixed