diff options
| author | bors <bors@rust-lang.org> | 2015-08-27 21:47:33 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2015-08-27 21:47:33 +0000 |
| commit | 79dd92fc1638463ab8af1d275686c4751ce91465 (patch) | |
| tree | 8f988bfd316630886eab6f2e98fded7ad77ab422 /src/libstd/sys/unix/stack_overflow.rs | |
| parent | abfa081c10c9401c8a2f858497fbac583bae234d (diff) | |
| parent | 6065678e627643cc3275c677408d11f48802595e (diff) | |
| download | rust-79dd92fc1638463ab8af1d275686c4751ce91465.tar.gz rust-79dd92fc1638463ab8af1d275686c4751ce91465.zip | |
Auto merge of #27930 - barosl:path_max, r=alexcrichton
This PR rewrites the code that previously relied on `PATH_MAX`. On my tests, even though the user gives the buffer length explicitly, both Linux's glibc and OS X's libc seems to obey the hard limit of `PATH_MAX` internally. So, to truly remove the limitation of `PATH_MAX`, the related system calls should be rewritten from scratch in Rust, which this PR does not try to do. However, eliminating the need of `PATH_MAX` is still a good idea for various reasons, such as: (1) they might change the implementation in the future, and (2) some platforms don't have a hard-coded `PATH_MAX`, such as GNU Hurd. More details are in the commit messages. Fixes #27454. r? @alexcrichton
Diffstat (limited to 'src/libstd/sys/unix/stack_overflow.rs')
0 files changed, 0 insertions, 0 deletions