Skip to content

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

Closed
Anipik opened this issue Dec 2, 2020 · 10 comments · Fixed by #45979
Labels
area-ILTools-coreclr untriaged New issue has not been triaged by the area owner

Comments

@Anipik
Copy link
Contributor

Anipik commented Dec 2, 2020

Darc updated the ilasm package version to 6.0 and we started hitting this

EXEC : warning : Classic PDB format is not supported on CoreCLR. [C:\git\runtime3\src\libraries\System.Runtime.CompilerServices.Unsafe\src\System.Runtime.CompilerServices.Unsafe.ilproj]

is this expected ?

@dotnet/runtime-infrastructure

@Dotnet-GitSync-Bot
Copy link
Collaborator

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-GitSync-Bot Dotnet-GitSync-Bot added the untriaged New issue has not been triaged by the area owner label Dec 2, 2020
@safern
Copy link
Member

safern commented Dec 2, 2020

Maybe something changed in arcade? I saw we hit this on the arcade update, right?

@ericstj
Copy link
Member

ericstj commented Dec 2, 2020

Hmm, I'd expect us to be using portable PDBs (as opposed to classic) everywhere now.

@ViktorHofer
Copy link
Member

I might be wrong but could this be connected to @ericstj's change where he stopped producing the old pdb format in libraries?

@ericstj
Copy link
Member

ericstj commented Dec 2, 2020

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.

@ericstj
Copy link
Member

ericstj commented Dec 2, 2020

So here is where the ILSDK maps DebugType property to commandline args to ILAsm, perhaps that needs some work?

<_IlasmSwitches Condition="'$(DebugType)' == 'Full'">$(_IlasmSwitches) -DEBUG</_IlasmSwitches>
<_IlasmSwitches Condition="'$(DebugType)' == 'Impl'">$(_IlasmSwitches) -DEBUG=IMPL</_IlasmSwitches>
<_IlasmSwitches Condition="'$(DebugType)' == 'PdbOnly'">$(_IlasmSwitches) -DEBUG=OPT</_IlasmSwitches>

@akoeplinger
Copy link
Member

See the discussion in #45387 (comment)

@radical
Copy link
Member

radical commented Dec 3, 2020

@radical radical added the blocking-clean-ci Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms' label Dec 3, 2020
@safern
Copy link
Member

safern commented Dec 3, 2020

@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 ILASM causing this, so I'm going to remove blocking-clean-ci as this is an issue on the ILASM version that we're updating to, but not manifesting on all PRs, just the PR trying to update that version.

@safern safern removed the blocking-clean-ci Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms' label Dec 3, 2020
@jkotas
Copy link
Member

jkotas commented Dec 11, 2020

This warning is not useful. I think we should get rid of this warning and always emit the portable PDBs.

jkotas added a commit to jkotas/runtime that referenced this issue Dec 11, 2020
I do not expect we will ever add the classic PDB support back in ilasm.

Fixes dotnet#45492
@ghost ghost added the in-pr There is an active PR which will close this issue when it is merged label Dec 11, 2020
jkotas added a commit that referenced this issue Dec 12, 2020
I do not expect we will ever add the classic PDB support back in ilasm.

Fixes #45492
@ghost ghost removed the in-pr There is an active PR which will close this issue when it is merged label Dec 12, 2020
@ghost ghost locked as resolved and limited conversation to collaborators Jan 11, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-ILTools-coreclr untriaged New issue has not been triaged by the area owner
Projects
None yet
Development

Successfully merging a pull request may close this issue.

8 participants