Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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.
Created attachment 3941 [details]
After upgrading runtime and now running Xamarin.Android 4.6.04000 with Visual Studio 2010 4.5.50709 SP1 Rel.
When trying to set a breakpoint, it stops and able to step but when running again the application hangs. If a manual break is initiated, the line where the original breakpoint was set is highlighted but cannot step or move beyond that point. Uninstalling and reinstalling does not help.
Test project where this is occurring is attached.
Version information below:
=== Xamarin Studio ===
Version 4.0.3 (build 13)
Installation UUID: 35cab5ab-caf0-4a95-8e1d-02fee4b0733f
Microsoft .NET 4.0.30319.17929
=== Xamarin.Android ===
Version: 4.6.4 (Enterprise Edition)
Android SDK: C:\Users\jfoster.DWYERMC\AppData\Local\Android\android-sdk
Supported Android versions:
2.1 (API level 7)
2.2 (API level 8)
2.3 (API level 10)
3.1 (API level 12)
4.0 (API level 14)
4.0.3 (API level 15)
4.2 (API level 17)
Java SDK: C:\Program Files (x86)\Java\jdk1.6.0_31
=== Build Information ===
Release ID: 400030013
Build date: 2013-03-21 15:53:00Z
Xamarin addins: 906a1edff23bcfd0ab7518463620a8ee506eaea2
=== Operating System ===
Windows 6.1.7601.65536 (64-bit)
I have been unable to replicate it using the information provided.
Is there any extra information on this? Which line is the break point set on? Which source file? a screencast would be helpful if possible.
Allie, I am unable to replicate this exact behaviour however it might be related to
Can we ask the customer to upgrade to the latest 4.8 (or 4.8.1 in beta) and see if the problem is resolved.
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.
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.