Bug 4698 - A breakpoint is never hit
Summary: A breakpoint is never hit
Status: RESOLVED FIXED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Debugger ()
Version: Trunk
Hardware: PC Linux
: --- normal
Target Milestone: ---
Assignee: Jeffrey Stedfast
URL:
Depends on:
Blocks:
 
Reported: 2012-04-27 12:45 UTC by Marek Safar
Modified: 2012-05-01 15:55 UTC (History)
1 user (show)

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


Attachments
test.cs (3.86 KB, text/x-csharp)
2012-04-27 12:46 UTC, Marek Safar
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 Marek Safar 2012-04-27 12:45:20 UTC
Set a breakpoint at line 53, it's never hit even if the execution hit the line
Comment 1 Marek Safar 2012-04-27 12:46:00 UTC
Created attachment 1766 [details]
test.cs
Comment 2 Jeffrey Stedfast 2012-04-27 17:19:17 UTC
I've fixed the breakpoint logic to break on the first ILOffset rather than the last ILOffset of the line (going onto the next line if the ILOffsets match).

fixed in git master
Comment 3 Marek Safar 2012-05-01 07:09:38 UTC
Heads up, this caused regression where breakpoint cannot be set to } else {. But the fix is correct we need working columns to properly fix } else { issue.
Comment 4 Jeffrey Stedfast 2012-05-01 15:55:50 UTC
ugh, good catch...