Assemblies saved with DeterministicMvid and portable pdbs cannot be loaded #583
Comments
mrvoorhe
added a commit
to Unity-Technologies/linker
that referenced
this issue
May 30, 2019
The test for mdb + deterministic mvid and portable pdb + deterministic mvid had to be ignored because they encounter jbevain/cecil#583
This was referenced May 30, 2019
|
Here is a PR to monolinker where I add tests that can reproduce this bug and #582 The tests that had to ignored were If you wanted to run the tests remove the |
marek-safar
pushed a commit
to dotnet/linker
that referenced
this issue
May 30, 2019
The test for mdb + deterministic mvid and portable pdb + deterministic mvid had to be ignored because they encounter jbevain/cecil#583
vargaz
added a commit
to vargaz/cecil
that referenced
this issue
May 30, 2019
…eds the guid of the corresponding assembly. Fixes jbevain#583.
|
Fixed by #587. |
mrvoorhe
added a commit
to Unity-Technologies/linker
that referenced
this issue
Jun 4, 2019
The test for mdb + deterministic mvid and portable pdb + deterministic mvid had to be ignored because they encounter jbevain/cecil#583
tkapin
pushed a commit
to tkapin/runtime
that referenced
this issue
Jan 31, 2023
The test for mdb + deterministic mvid and portable pdb + deterministic mvid had to be ignored because they encounter jbevain/cecil#583 Commit migrated from dotnet/linker@d24b2e7
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I was using
DeterministicMvidin monolinker and had an assembly with portablepdbs. monolinker was able to strip and write the assembly without issue. However, if anything tries to read that assembly back inModuleDefinition.ReadSymbols()throws aSymbolsNotMatchingExceptionexception. See #582 for more details.The text was updated successfully, but these errors were encountered: