Bug 10907 - Debugging skipping breakpoints
Summary: Debugging skipping breakpoints
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: Android ()
Version: unspecified
Hardware: PC Windows
: High normal
Target Milestone: ---
Assignee: dean.ellis
Depends on:
Reported: 2013-03-05 09:29 UTC by Joshua Barker
Modified: 2016-08-03 15:24 UTC (History)
6 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 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 Joshua Barker 2013-03-05 09:29:44 UTC
Getting "Source Not Available – Code not running" a lot of times when trying to break at a breakpoint.
Comment 1 Mikayla Hutchinson [MSFT] 2013-03-07 15:22:32 UTC
What kind of app is this? What versions?
Comment 2 Joshua Barker 2013-03-07 16:30:27 UTC
A regular monodroid app with no native Java. Version 4.6.
Comment 3 Mikayla Hutchinson [MSFT] 2013-03-07 17:53:34 UTC
Do you have the same problem if you use Xamarin Studio?
Comment 4 Joshua Barker 2013-03-08 08:01:22 UTC
I typically don't use Xamarin Studio, but in a little bit of testing it doesn't appear to be happening.
Comment 5 PJ 2013-11-19 17:04:00 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 6 Joshua Barker 2013-11-19 17:14:19 UTC
haven't been able to duplicate it with newer version