-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
PGO Instrumented SDK fails to load coreclr.dll #95534
Comments
This was broken by #89311. The problem is that the PGO instrumented coreclr.dll depends on pgort140.dll. pgort140.dll is copied locally next to coreclr.dll. The flag added by #89311 enforces that coreclr.dll can only depend on system .dlls. Locally copied pgort140.dll is not a system .dll and that leads to the coreclr.dll load failure. @DrewScoggins @AustinWise @elinor-fung Do you have opinions about the best way to proceed? I can think about two options:
|
Personally, I like the second option if it is available. The linker should not be affected by the In terms of risks of reverting #89311, the risk is low. This is a defense-in-depth type protection. Reverting it does not expose any known security problems. I don't believe BinSkim currently checks this flag, so CI should not complain. |
Ok, I have opened https://devdiv.visualstudio.com/DevDiv/_queries/edit/1924842/ (internal MS link) to get a fix in the linker. Let's revert #89311 for now to get the PGO data flow unblocked. |
This all sounds good to me. We are still waiting on this change to flow through to the installer, but once it makes it in I will make sure we get another run going to make sure this fixed the issue. |
Fixed by #95540 |
I have opened #95598 to revert the revert once the PGO collection issue is resolved. |
When trying to run
dotnet
runtime startup fails and prints the following error messageYou can obtain a copy of the instrumented SDK from here. I took a quick look at this is
windbg
, but all I could find is that we were getting an access violation when this error is printed. I couldn't find any symbols so I don't know where we were in startup.Tagging @jkotas for routing.
The text was updated successfully, but these errors were encountered: