Re: PATH_MAX

[Jim Meyering]

Neal H Walfield <address@hidden> wrote:
>> +/* Distinguish between the cases when pathconf fails and when it reports 
>> there
>> +   is no limit (the latter is the case for PATH_MAX on the Hurd).  When 
>> there
>> +   is no limit, return LONG_MAX.  Otherwise, return pathconf's return 
>> value.  */
>
> Are you sure that you really want to do this?  You use the result of

For pathchk.c, I think it's fine.
Obviously in other cases that won't work at all and I'll have
to use a different approach.

> this in a variety of places as arrays on the stack.  This is basically
> guaranteed to cause a seg fault.  Even if you changed that code to use
> malloc, this is still way to large.