Fix stack overflow in gdlpp when handling CR line endings#50
Open
bgermann wants to merge 1 commit intosilnrsi:masterfrom
Open
Fix stack overflow in gdlpp when handling CR line endings#50bgermann wants to merge 1 commit intosilnrsi:masterfrom
bgermann wants to merge 1 commit intosilnrsi:masterfrom
Conversation
The \r handling code in get() uses a recursive call to get() to peek at the next character. On files using bare \r line endings (classic Mac), every line triggers a nested get() call, leading to unbounded stack growth and a crash. Replace the recursive get()/unget() with a direct buffer peek, which correctly handles \r\n, bare \r, and \n without recursion.
bgermann
force-pushed
the
debian-715950
branch
from
4e644ca to
3788a95
Compare
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
1 participant
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.
The \r handling code in get() uses a recursive call to get() to peek at the next character. On files using bare \r line endings (classic Mac), every line triggers a nested get() call, leading to unbounded stack growth and a crash.
Replace the recursive get()/unget() with a direct buffer peek, which correctly handles \r\n, bare \r, and \n without recursion.
Fixes #5.