Avoid out-of-bound access on corner cases / when readlink fails. #14
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.
When looking if I could enable Hurd support (Hurd does not have PATH_MAX), I spotted these two out-of-bound bugs in getExecutablePath()
if readlink fails, (returns -1), but the fallback worked, ret will still be -1, so the code will "Nul-Terminate" at buf[-1] (
readlink might return PATH_MAX. In this case, the nul termination will write buf[PATH_MAX], one byte beyond the array.
For this, it is easiest to just allocate 1 byte more for the array.