Skip to content
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

Generated strings should be null terminated #16

Closed
TethysSvensson opened this issue Dec 19, 2021 · 1 comment
Closed

Generated strings should be null terminated #16

TethysSvensson opened this issue Dec 19, 2021 · 1 comment

Comments

@TethysSvensson
Copy link
Collaborator

TethysSvensson commented Dec 19, 2021

I don't know if they are already null terminated, but in any case we also need to add a test for it.

@TethysSvensson TethysSvensson changed the title Double check if our generated strings are null terminated Generated strings should be null terminated Dec 26, 2021
TethysSvensson added a commit that referenced this issue Jan 4, 2022
TethysSvensson added a commit that referenced this issue Jan 4, 2022
* Adds null terminators to the end of written strings to fix issue #16
* Adds optional null terminator validation while deserializing gated
  behind a new `extra-validation` feature flag.
* Adds extensive testing for the fix.
* Slightly changes the debug output for deserialized tables.
TethysSvensson added a commit that referenced this issue Jan 4, 2022
* Add null terminators to strings

* Adds null terminators to the end of written strings to fix issue #16
* Adds optional null terminator validation while deserializing gated
  behind a new `extra-validation` feature flag.
* Adds extensive testing for the fix.
* Slightly changes the debug output for deserialized tables.

* Add safety comments
@TethysSvensson
Copy link
Collaborator Author

Fixed in #36.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant