Skip to content
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 bind to CoreCLR on Windows #47079

Open
caaavik-msft opened this issue Feb 25, 2025 · 2 comments
Open

PGO Instrumented SDK fails to bind to CoreCLR on Windows #47079

caaavik-msft opened this issue Feb 25, 2025 · 2 comments
Labels
untriaged Request triage from a team member

Comments

@caaavik-msft
Copy link

caaavik-msft commented Feb 25, 2025

Describe the bug

We are unable to run the dotnet-optimization pipeline against the latest PGO instrumented SDK version as it gives the following error on running dotnet --info:

Failed to load [D:\a\_work\1\s\artifacts\out\sdk\x64\shared\Microsoft.NETCore.App\10.0.0-preview.2.25119.7\coreclr.dll], HRESULT: 0x8007007E
Failed to bind to CoreCLR at 'D:\a\_work\1\s\artifacts\out\sdk\x64\shared\Microsoft.NETCore.App\10.0.0-preview.2.25119.7\'
Failed to create CoreCLR, HRESULT: 0x80008088

To Reproduce

  1. Download the latest PGO instrumented SDK (e.g. https://ci.dot.net/public/Sdk/10.0.100-preview.3.25124.13/dotnet-sdk-pgo-10.0.100-preview.3.25124.13-win-x86.zip)
  2. Unpack the zip
  3. Run dotnet.exe --info

Further technical details

This is reproducing for Windows x86, x64, and arm64 pipelines, but is not reproducing on Linux.

The last known working version of the SDK which doesn't reproduce this error is 10.0.100-alpha.1.24619.16. Unfortunately I don't have a better SDK version range to share at the moment to isolate what caused this issue as we had a separate unrelated issue on the dotnet-optimization pipeline that meant we don't have pipeline runs on SDK versions in between that range.

Copy link

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

@dotnet-issue-labeler dotnet-issue-labeler bot added the untriaged Request triage from a team member label Feb 25, 2025
Copy link

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
untriaged Request triage from a team member
Projects
None yet
Development

No branches or pull requests

1 participant