fixes parsing section and region statements #9
Conversation
This file contains hidden or 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
Note: this is a backport from bap-1.3.1 package, as this fix is already there, but wasn't commited to the master branch of the upstream repository. The fix enables the special handling for the Section and Region types, which use hex number without the 0x prefix. Ideally, we shouldn't generate such input, but since historically this happened, we need to make our parser robust enough to be able to chew such representation also.
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.
Note: this is a backport from bap-1.3.1 package, as this fix is
already there, but wasn't commited to the master branch of the
upstream repository.
The fix enables the special handling for the Section and Region types,
which use hex number without the 0x prefix. Ideally, we shouldn't
generate such input, but since historically this happened, we need to
make our parser robust enough to be able to chew such representation
also.