Fix null pointer dereference in ngram_model_read#438
Merged
Conversation
dhdaines
approved these changes
Oct 23, 2025
Contributor
dhdaines
left a comment
There was a problem hiding this comment.
Argh! Yes another one of these error string formatting issues. The NULL pointer check is totally sensible as well.
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
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.
Description
Fixes a null pointer dereference when reading malformed or empty ARPA language model files.
The NGRAM_ARPA case in
ngram_model_readdid not check if the model was NULL before proceeding, unlike other file type cases. This caused a crash inngram_model_apply_weightswhen processing invalid files.Changes:
ngram_model_trie_read_arpacallVerification steps
Fixes #432