-
Notifications
You must be signed in to change notification settings - Fork 5k
Hitting Classic PDB format is not supported on CoreCLR. while using 6.0 version of the ILASM package #45492
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
Comments
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. |
Maybe something changed in arcade? I saw we hit this on the arcade update, right? |
Hmm, I'd expect us to be using portable PDBs (as opposed to classic) everywhere now. |
I might be wrong but could this be connected to @ericstj's change where he stopped producing the old pdb format in libraries? |
I changed it the other way. That warning indicates that the build is asking ILAsm to produce classic PDB which is not what we want. |
So here is where the ILSDK maps runtime/src/coreclr/src/.nuget/Microsoft.NET.Sdk.IL/targets/Microsoft.NET.Sdk.IL.targets Lines 131 to 133 in b9de3d0
|
See the discussion in #45387 (comment) |
@radical PR #45451 I don't think it hit this error, it actually hit a networking issue on the Browser leg and the other is a test failure (Unless I'm missing something). PR #45387 is the PR that is updating the version of |
This warning is not useful. I think we should get rid of this warning and always emit the portable PDBs. |
I do not expect we will ever add the classic PDB support back in ilasm. Fixes dotnet#45492
I do not expect we will ever add the classic PDB support back in ilasm. Fixes #45492
Uh oh!
There was an error while loading. Please reload this page.
Darc updated the ilasm package version to 6.0 and we started hitting this
is this expected ?
@dotnet/runtime-infrastructure
The text was updated successfully, but these errors were encountered: