Bug 13492 - Inconsistent variable values in methods with default parameters
Summary: Inconsistent variable values in methods with default parameters
Status: RESOLVED FIXED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Debugger ()
Version: unspecified
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Jeffrey Stedfast
URL:
Depends on:
Blocks:
 
Reported: 2013-07-25 22:47 UTC by Emil H.
Modified: 2013-07-26 01:52 UTC (History)
3 users (show)

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


Attachments
Inconsistency when examining variables while debugging (86.93 KB, image/png)
2013-07-25 22:47 UTC, Emil H.
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 Emil H. 2013-07-25 22:47:37 UTC
Created attachment 4444 [details]
Inconsistency when examining variables while debugging

When examining a stack frame of a method that has default parameters, hovering over the variable will display the default parameter value rather than the real value. The Locals view displays the correct value however.
Comment 1 Alan McGovern 2013-07-26 01:52:08 UTC
We've recently fixed several issues with the debugger tooltips, including this issue. I don't believe the fixes landed in time for the next beta release, which should be Xamarin Studio 4.1.8, but they will be in the subsequent release.

Thanks for reporting the issue