-
-
Notifications
You must be signed in to change notification settings - Fork 624
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
ReadDebugHeader method change causing a SymbolsNotMatchingException #589
Comments
The check is necessary as we've probably seen empty debug headers. It should however be possible to change the check to verify that |
Coming back with the test dll. I have managed to create a ikvm generated test dll with 7.1.4532.2 . Attaching the dll and pdb here. The problem can easily be reproduced with a test inside PdbTests and these assemblies.
|
Thanks for the test, unfortunately it's not self contained and requires to resolve at least IKVM.Runtime, so I can't take the test as it is. I've pushed a quick fix, but would love a self contained test. |
Thank you for the quick fix! Indeed I saw that the test was failing for the ReadImmediately use case with the fix you mentioned. I've added the IKVM.Runtime.dll as well in this commit, if you want to add a self contained test. |
Another quick question, do you know when 0.11 will be released? Perhaps even a beta version we could reference. |
Hi,
In #349 the ReadDebugHeader method was changed, and we now check
inside
We have a scenario in which we use il-repack to merge dlls (together with pdbs). Currently il-repack is using the old version of Cecil and this part works. We want to unfork cecil in gluck/il-repack#236 and use the current version but it seems that symbol files for IKVM'ed dlls are not read correctly now.
I tracked down the issue to that part of the code. In our IKVM symbol file the
AddressOfRawData
is 0. But the PointerToRawData is correct and if we skip that check (using debugger) then the behavior works as before.Is that check necessary? Can we remove it?
Unfortunately I can't add the dll plus pdb which are problematic but I will try to generate dummy dlls and attach them here.
Thank you
The text was updated successfully, but these errors were encountered: