-
Notifications
You must be signed in to change notification settings - Fork 6
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
Missing check of size and alignment of opaque fields #288
Comments
Shouldn't we just reject the model in such cases? Do we know of examples that have non-byte-aligned opaque fields? |
You are right. I thought there would be an example, but I couldn't find one. So we should check that in the model. |
Even if there were examples. How would we write and read the fields without getters and setters? Aside from that the properties to prove the length was:
This also requires that the message itself is also byte aligned. If this is not the case the |
That is true. I cannot see a way to misalign a message as soon as the alignment is checked for opaque fields. |
The generated getters and setters for opaque fields assume that the field is byte-aligned and its bit length is a multiple of 8. This is currently not ensured.
Getters and setters for opaque fields should be only generated if these assumptions are met.We should check that in the model.The text was updated successfully, but these errors were encountered: