Bug 53026 - Unknown application "vmmap" asking for debugging permission, when debugging a .NET Core app for the first time
Summary: Unknown application "vmmap" asking for debugging permission, when debugging a...
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Debugger (show other bugs)
Version: 7.0 (VSforMac)
Hardware: Macintosh Mac OS
: Low minor
Target Milestone: Future Cycle (TBD)
Assignee: David Karlaš
Depends on:
Reported: 2017-03-03 19:02 UTC by Manish Sinha
Modified: 2017-04-04 06:36 UTC (History)
3 users (show)

See Also:
Is this bug a regression?: ---
Last known good build:

Screenshot (60.66 KB, image/png)
2017-03-03 19:04 UTC, Manish Sinha

Description Manish Sinha 2017-03-03 19:02:53 UTC
Steps to reproduce

1. Create a .NET Core app
2. Set a breakpoint
3. Run

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

Ide.log: https://gist.github.com/manish/a854681981ff0b596019f894a2b09033
Comment 1 Manish Sinha 2017-03-03 19:04:24 UTC
Created attachment 20125 [details]
Comment 2 Vsevolod Kukol 2017-03-06 19:00:16 UTC
I can't reproduce this issue, VS never asked me for permission. Could it depend on the .NET Core version?

cc @Matt
Comment 3 Matt Ward 2017-03-06 19:08:16 UTC
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.
Comment 4 David Karlaš 2017-03-23 12:24:29 UTC
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...)
Comment 5 Matt Ward 2017-03-23 13:56:56 UTC
Still happening for me with a fairly recent build of VS Mac from master.
Comment 6 David Karlaš 2017-03-27 13:28:13 UTC
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...
Comment 7 David Karlaš 2017-04-04 06:36:06 UTC
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...

Note You need to log in before you can comment on or make changes to this bug.