-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dbgshim.dll!RegisterForRuntimeStartup can incorrectly fail with E_ACCESSDENIED on Windows #8717
Comments
Are the local simulator processes an internal testing or a production scenario? |
That depends on your definition of 'production' -- this is how customers develop Azure Service Fabric applications on their dev box's. The problem might also exist with in-the-cloud debugging, but I am not sure if such a feature exists for Service Fabric. |
Changed the open process token from TOKEN_READ to TOKEN_QUERY.
Changed the open process token from TOKEN_READ to TOKEN_QUERY.
Changed the open process token from TOKEN_READ to TOKEN_QUERY.
BTW: I recommend to keep servicing issues opened, until they are merged into 2.0 servicing branch. |
This is approved for checkin when the branch is open for 2.0.2. |
Fixed issue #13282: dbgshim fails with E_ACCESSDENIED on Windows.
This was merged for 2.0.1. Closing now. |
RegisterForRuntimeStartup is requesting TOKEN_READ access when it should request TOKEN_QUERY access.
Here is the line of code with the bug: https://github.com/dotnet/coreclr/blob/32f0f9721afb584b4a14d69135bea7ddc129f755/src/utilcode/securityutil.cpp#L339
This prevents RegisterForRuntimeStartup from working correctly with Azure Service Fabric local simulator processes.
The text was updated successfully, but these errors were encountered: