read branch targets as signed integers #18
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mike-hunhoff
approved these changes
Jun 30, 2022
|
Thank you for catching this! Yes as mentioned in our README dncil is based on the CIL parsing code found in dnlib. I have opened a new issue to double-check the types emitted by dncil's reader. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As defined by the standard for CIL code, targets of branch and switch instructions are stored as signed offsets [ECMA 335, Chapter III, 3.15 and 3.66].
Dncil previously read unsigned values in those cases, which caused issues for me. This is now fixed.
The code is probably based on dnlib, which in fact reads unsigned values and works just fine. Because dnlib is written in C#, an overflow will occur when negative offsets are encountered, so it still behaves like signed values were read. Such overflows do not occur in python, so the implementation has to differ from dnlib here.
There might be more of such issues hidden somewhere. Maybe it would be worth comparing the rest of the reader code to the specification as well...