Bug 1481 - Unable to inspect static variable from parent class
Summary: Unable to inspect static variable from parent class
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Debugger ()
Version: Trunk
Hardware: PC Windows
: High major
Target Milestone: master
Assignee: Mike Krüger
: 2113 ()
Depends on:
Reported: 2011-10-13 14:37 UTC by Jonathan Pobst
Modified: 2015-08-20 03:24 UTC (History)
5 users (show)

Tags: resolver
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 Jonathan Pobst 2011-10-13 14:37:49 UTC
In the following test case, if you set a breakpoint at the CWL in DoStuff, you cannot inspect the "test_var" variable.  It returns: "Unknown identifier: test_var".  You can inspect it when in Main ().

using System;

namespace debugtest
	class MainClass
		static bool test_var = false;
		public static void Main (string[] args)
			var tc = new TestClass ();
			tc.DoStuff ();
			Console.WriteLine (test_var);
		class TestClass
			public void DoStuff ()
				Console.WriteLine (test_var);   // bp here
Comment 1 Jeffrey Stedfast 2011-12-09 18:46:26 UTC
This depends on the resolver, so this should be fixed on the newresolver branch but it's broken even worse there :-(


TextEditorResolverProvider.cs:GetLanguageItem() needs to actually set the DomRegion to the proper line/column values so that DebugValueTooltipProvider.cs:GetItem() can properly get the DocumentLocation start/end offsets and call ed.GetTextBetween (start, end);

FWIW, you've got a TODO comment in TextEditorResolverProvider.cs:GetLanguageItem() about implementing this :-)
Comment 2 Mikayla Hutchinson [MSFT] 2011-12-12 10:29:36 UTC
Does this completely break debugger tooltips on newresolver then?
Comment 3 Jeffrey Stedfast 2011-12-12 18:03:17 UTC
*** Bug 2113 has been marked as a duplicate of this bug. ***
Comment 4 Alan McGovern 2012-01-10 21:31:09 UTC
Debugging tooltips are still broken on newresolver.
Comment 5 Mike Krüger 2012-01-11 02:42:20 UTC
At least the newresolver can resolve this variable case.
Comment 6 Mike Krüger 2012-02-15 06:22:37 UTC
Should work in new resolver.