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 for Bug 53026 on
Developer Community or GitHub if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
Steps to reproduce
1. Create a .NET Core app
2. Set a breakpoint
Expected: Debugger starts and breakpoint is hit
Actual: A permission dialog shows up with "vmmap" asking for debugging permission
The user does not know what this "vmmap" is
About XS: https://gist.github.com/manish/28302986e15c737e7f110fd1641db9e2
Created attachment 20125 [details]
I can't reproduce this issue, VS never asked me for permission. Could it depend on the .NET Core version?
It is not specific to VS for Mac. It is possible to reproduce it with Visual Studio Code. It only happens the one time until you reboot the entire machine again. I have seen it with every .NET Core version I have used.
Is this still happening with latest VSfM? Because i believe I saw this in past, but even after restarting I can't reproduce(.NET Core debugging adapter changed a lot recently, maybe this is the reason...)
Still happening for me with a fairly recent build of VS Mac from master.
Since this is also happening on VSCode I'm closing this as upstream bug, I also email .NET Core debugger team if something can be done about this...
What we should do is check if `DevtoolsSecurity`(command line tool) is enabled, and if its not before starting debugging ask developer to enable it, like XCode does...