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 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 19483 [details]
Screenshot of debugger stack when breaking
The first, most obvious symptom of the problem is that breakpoints aren't being hit. The second comes when you break and look at the call stack: the stack frames of my app are grayed out, while the stack frames for the framework are "active". Sure enough, when I turn on "Just My Code", the stack frames from my app disappear, including the app Main method. See the attached screenshot for an example.
Version info is as follows:
Microsoft Visual Studio Enterprise 2017 RC
Version 15.0.26020.0 D15REL
Microsoft .NET Framework
Installed Version: Enterprise
Visual Basic 2017 RC 00369-50000-00000-AA859
Microsoft Visual Basic 2017 RC
Visual C# 2017 RC 00369-50000-00000-AA859
Microsoft Visual C# 2017 RC
Visual F# 4.1 00369-50000-00000-AA859
Microsoft Visual F# 4.1
Application Insights Tools for Visual Studio Package 8.4.01118.2
Application Insights Tools for Visual Studio
ASP.NET and Web Tools 2016 15.0.21206.0
ASP.NET and Web Tools 2016
ASP.NET Web Frameworks and Tools 2013 5.2.41123.0
For additional information, visit https://www.asp.net/
Azure App Service Tools v2.9.6 15.0.21130.0
Azure App Service Tools v2.9.6
Command Bus, Event Stream and Async Manager Merq
Provides ICommandBus, IEventStream and IAsyncManager MEF services for loosely coupled Visual Studio extension components communication and integration.
Common Azure Tools 1.8
Provides common services for use by Azure Mobile Services and Microsoft Azure Tools.
KofePackagePackage Extension 1.0
KofePackagePackage Visual Studio Extension Detailed Info
Microsoft Continuous Delivery Tools for Visual Studio 0.1
Simplifying the configuration of continuous build integration and continuous build delivery from within the Visual Studio IDE.
Microsoft MI-Based Debugger 1.0
Provides support for connecting Visual Studio to MI compatible debuggers
Mono Debugging for Visual Studio Mono.Debugging.VisualStudio
Support for debugging Mono processes with Visual Studio.
NuGet Package Manager 4.0.0
NuGet Package Manager in Visual Studio. For more information about NuGet, visit http://docs.nuget.org/.
SQL Server Data Tools 15.1.61124.0
Microsoft SQL Server Data Tools
Zero friction testing for Visual Studio
TSCPackage Extension 1.0
TSCPackage Visual Studio Extension Detailed Info
TypeScript tools for Visual Studio
VsVim 188.8.131.52 Debug
VsVim is a Vim emulator for Visual Studio
Xamarin 184.108.40.2069 (7c3dcf2)
Visual Studio extension to enable development for Xamarin.iOS and Xamarin.Android.
Xamarin.Android 220.127.116.11 (72366f7)
Visual Studio extension to enable development for Xamarin.Android.
Xamarin.iOS 10.4.0.33 (d93ae7e)
Visual Studio extension to enable development for Xamarin.iOS.
Also, the Modules window is completely empty and the Disassembly window says "No disassembly available"
Andy, do you get exceptions if you force them? For instance, if you throw a NullReferenceException on any interaction? There was a bug in 2017 where the debugger will not be installed at all. In that case, you will get the behavior you describe plus exceptions will crash the app but not show in VS. If that's the case, then I can give you steps to fix locally (that's already fixed in newer builds). If it's not, I'll need to review. The first and most important thing is to get your output in the Debug Output when the app is running. Build logs should be fine too if you have them (detailed).
The debugger does get break on exceptions if they are thrown and I can see the exception Instance in the locals window and examine it (look at the message, stack trace, etc.)
Created attachment 19491 [details]
Output from Debug pane
Cool, then it looks like a different bug. I'll try a repro and fix. Moving to SR1.
Looking back into this, the problem seems to be that the breakpoints end up in the wrong locations in the lambdas. Is this still happening after the latest fixes (meaning, in the latest version)? I'm not being able to properly repro.
Just tested this with VS 2017 15.2 (26430.16) and it no longer seems to repro. Seems to have been fixed.
Excellent, Andy, thanks. I'll mark as fixed. Please do reopen if it happens again.
Created attachment 23998 [details]
Attached IDE logs
The debugger is working fine as expected in 2017, hence this issue doesn't reproducible anymore
Environment info :
Screencast link : https://www.screencast.com/t/AGPbX9E9C0Zx