Bug 9421 - VS2012: Breakpoints don't work if set after we've run through the code once
Summary: VS2012: Breakpoints don't work if set after we've run through the code once
Alias: None
Product: Android
Classification: Xamarin
Component: Debugger ()
Version: 4.4.x
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2013-01-09 10:22 UTC by Jeremy Kolb
Modified: 2013-12-05 18:36 UTC (History)
2 users (show)

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 Jeremy Kolb 2013-01-09 10:22:29 UTC
If I run through a function and there's an exception and I set a breakpoint and run through the function again the breakpoint is ignored.  Instead I hit a non-existant breakpoint at the end of the file.
Comment 1 dean.ellis 2013-03-07 07:31:52 UTC
are you able to provide a sample application which demonstrates the issue, I have tried to replicate by calling the following method in a button click

private void Test()
  try {
	throw new Exception("boo");
  } catch (Exception) {

After running through the method once, I can set a break point on the throw statement and the debugger breaks at that point. 

I am using VS2012.
Comment 2 PJ 2013-11-19 17:05:55 UTC
This bug has been in the NEEDINFO state with no changes for the last 90 days. Can we put this back into the NEW or CONFIRMED state, or are we still awaiting response?

If there is no change in the status of this bug over the next two weeks, this bug will be marked as NORESPONSE.
Comment 3 PJ 2013-12-05 18:36:22 UTC
This bug has not been changed from the NEEDINFO state since my previous comment, marking as RESOLVED NORESPONSE.

Please feel free to REOPEN this bug at any time if you are still experiencing the issue. Please add the requested information and set the bug back to the NEW (or CONFIRMED) state.