Bug 5328 - Adding lines to source code on code pause causes the stepper to highlight wrong lines
Summary: Adding lines to source code on code pause causes the stepper to highlight wro...
Status: RESOLVED DUPLICATE of bug 2853
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: General ()
Version: unspecified
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2012-05-25 08:37 UTC by Gary____
Modified: 2012-05-25 11:13 UTC (History)
1 user (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 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 DUPLICATE of bug 2853

Description Gary____ 2012-05-25 08:37:52 UTC
If execution stops at a break point, and i add 1 line of code after that breakpoint (usually a comment about something i noticed via inspection or the immediate window) the yellow line indication point of execution as i step through the rest of the class is off by 1 line

Windows 3.2
Comment 1 Mikayla Hutchinson [MSFT] 2012-05-25 11:13:43 UTC
Once the source no longer matches what was used to compile, locations can't be reliably correct. The best solution is to warn the user.

*** This bug has been marked as a duplicate of bug 2853 ***