VAM Constraint Check Loop Fix #276
Closed
+24
−3
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
|
Owner
|
Ha, this issue just sounded too familiar and it is, see ika-rwth-aachen/etsi_its_messages#77 |
Owner
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Recently, I'm trying to use
its::r2::Vamin my code. I encountered an issue while validating the message. It basically causes an infinite loop while checking the VAM header constraints. The commit dae0283 is just for reproducing the error. Please confirm the issue. And the commit b861330 is just a workaround even I know this file is a generated file by asn1c and shouldn't be edited directly. I couldn't find the origin of the error and I'm not sure if it affects other generated files. The fix can be revised for a more clean approach.