fix: handle integer suffix in #line directive without crashing#601
Merged
Conversation
Closes eliben#587 Signed-off-by: Sai Asish Y <say.apm35@gmail.com>
eliben
approved these changes
May 25, 2026
Owner
|
Thanks for the contribution! |
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.
A
#linedirective with an integer suffix (e.g.#line 0u) caused an unhandledValueError: invalid literal for int() with base 10: '0u'inc_lexer.py. The_decimal_constantregex already accepts suffixes likeu/U/l/L, so a fuzz-generated input with a suffixed line number reachesint(pp_line)and crashes.This wraps the
int()call in atry/except ValueErrorand reports a proper"invalid #line directive"parse error instead. Three tests added toTestCLexerErrors.test_preprocessorcovering0u,1U, and10uLL.Closes #587