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.
1. Create console application in XS
2. Set Breakpoint
3. Debug the application
Application debug successfully and breakpoint does not hit.
On debugging application breakpoint should hit.
Regression Status: REGRESSION. This issue does not exist with Stable Xamarin Studio Version 4.0.12 (build 3) and on debugging the application breakpoint hits successfully.
=== Xamarin Studio ===
Version 4.0.13 (build 31)
Installation UUID: 1a4f208c-e41a-4374-916d-8e86d606fb42
Microsoft .NET 4.0.30319.18051
GTK+ 2.24.20 theme: MS-Windows
=== Xamarin.Android ===
Version: 4.8.2 (Enterprise Edition)
Android SDK: C:\Users\Administrator\AppData\Local\Xamarin\MonoForAndroid\AndroidSDK
Supported Android versions:
2.1 (API level 7)
2.2 (API level 8)
2.3 (API level 10)
3.1 (API level 12)
3.2 (API level 13)
4.0 (API level 14)
4.0.3 (API level 15)
4.1 (API level 16)
4.2 (API level 17)
4.3 (API level 18)
Java SDK: C:\Program Files\Java\jdk1.7.0_25
java version "1.7.0_25"
Java(TM) SE Runtime Environment (build 1.7.0_25-b17)
Java HotSpot(TM) Client VM (build 23.25-b01, mixed mode, sharing)
=== Build Information ===
Release ID: 400130031
Build date: 2013-09-17 13:42:23Z
Xamarin addins: a6908312c9ad3e40f09ad731f444cad06ddf1546
=== Operating System ===
Nothing changed in the Windows debugger from 4.0.12 to 4.0.13.
I have checked this issue again and I am still getting same issue with XS 4.0.13 (build 31).
Here I am observing one more thing that 'Start Debugging' option under Run menu appears as disabled and when I debug application by clicking Run button then break point does not hit.
With stable XS 4.0.12 (build 3) 'Start Debugging' option under Run menu appears as enabled and when I debug application by clicking Run button then break point hits successfully.
Are you using the .NET debugger or the Mono Soft Debugger?
We are using Mono Soft Debugger.
It uses the first debugger in the list that's compatible with the target runtime.
Looks like the windows debugger is missing?
Lluis, any thoughts? I fixed up the WiX scripts as best I could after moving the debugger, but it doesn't look like it worked.
The problem here is that it's not running under a debugger at all, I bet.
I'm having the same problem with 4.0.13 Build 38. The only debugger listed under Options are Mono Soft debuggers. Is there a way to hook into the .NET debugger using XS?
Jeffrey, you are right. I have all "debug" centric menu items disabled on Windows.
Today we have checked this issue on following builds :
XS 4.1.7 (build 1524)
Now user able to hit break point for console application.
But it hits breakpoint even in Release mode. So we filed another bug 15586 and closing this issue.