Bug 2511 - Debugger breakpoints do not hit on Android
Summary: Debugger breakpoints do not hit on Android
Status: RESOLVED DUPLICATE of bug 2196
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Android Add-in ()
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: shana@xamarin.com
Depends on:
Reported: 2011-12-14 21:49 UTC by John Moore
Modified: 2011-12-22 21:23 UTC (History)
1 user (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 John Moore 2011-12-14 21:49:30 UTC
In monodevelop set a breakpoint on code file on mono 4 android project
debug app (debugger does not always connect, I think this is related to bug 2495,) emulator or physical device i'm seeing same behavior
if debugger connects, after the app starts the break point is colored white with a red outline (i think that means the break point is not in loaded code/assembly???)
break point is not hit; however exceptions are caught and the exception dialog is displayed within MD.

I think this is related to, a direct result of, or a duplicate of bug 2495.
Windows 7 64
MD 2.8.5
M4A 4.0.1
Comment 1 John Moore 2011-12-22 21:23:47 UTC

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