Re: [PATCH] test-getcwd: don't stack-allocate PATH_MAX bytes

On 06/20/2011 04:43 PM, Bruno Haible wrote: > Eric Blake wrote: >> --- a/tests/test-getcwd.c >> +++ b/tests/test-getcwd.c >> @@ -26,7 +26,6 @@ >> #include >> #include >> >> -#include "pathmax.h" >> #include "macros.h" >> >> #if ! HAVE_GETPAGESIZE >> > > Hmm, this will now cause test_long_nam

Re: [PATCH] test-getcwd: don't stack-allocate PATH_MAX bytes

Eric Blake wrote: > --- a/tests/test-getcwd.c > +++ b/tests/test-getcwd.c > @@ -26,7 +26,6 @@ >  #include >  #include > > -#include "pathmax.h" >  #include "macros.h" > >  #if ! HAVE_GETPAGESIZE > Hmm, this will now cause test_long_name to return immediately on HP-UX, without performing a tes

[PATCH] test-getcwd: don't stack-allocate PATH_MAX bytes

This reverts commit 1e33f8d86f, which guarantees that PATH_MAX is always defined (but not necessarily constant). Rather, the test-getcwd code should be robust to POSIX rules for unlimited or varying length maximums; as well as still passing in spite of the HP-UX bug that doesn't define PATH_MAX as