Avoid use of PATH_MAX (Debian bug #1009066) #98
Closed
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.
PATH_MAX is undefined on GNU Hurd (as is allowed by POSIX), and is in
some regards problematic anyway (cf
https://www.gnu.org/software/hurd/hurd/porting/guidelines.html#PATH_MAX_tt_MAX_PATH_tt_MAXPATHL
).
This patch from Yavor Doganov instead dynamically allocates
*resolvedpath
as necessary usingrealpath(childpath, NULL)
(andthen makes sure to free it later).
Signed-off-by: Matthew Vernon [email protected]