Fix issues in code #79
Merged
Conversation
This file contains 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
realloc cannot guaranteed to use same location which is why the pointer needs to be reassigned
the original implementation tried driving p1 ahead resulting in an invalid read once we reach the null termination fixed by checking p1 and incrementing it later fixed bad function signature, we cannot return const char* as char*
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.
strreplacemakes use ofreallocwhich does not guarantee to reuse the same location in memory, thus the pointer needs to be reassaignedstrstr_iimplementation, it ran ahead of p1 and read 1 byte out of boundsstrstr_isignature, previously it discarded const on return