From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: segfault with exceedingly long path
Date: Sun, 19 Jan 2014 13:35:50 -0800 [thread overview]
Message-ID: <140119133550.ZM5354@torch.brasslantern.com> (raw)
In-Reply-To: <20140119191048.018a051a@pws-pc.ntlworld.com>
On Jan 19, 7:10pm, Peter Stephenson wrote:
}
} I'm still in favour of reducing dependency on PATH_MAX wherever
} possible, since any arbitrary limit we don't actually need we don't
} actually want
In this particular case even if the shell were able to deal with an
"unlimited" directory nesting depth, system calls like chdir(2) would
begin to fail. fchdir() sort of works around it by not passing the
path name, but you still must somehow obtain a file descriptor to the
directory, so it's just pushing the problem up a level.
next prev parent reply other threads:[~2014-01-19 21:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-18 0:20 Axel Beckert
2014-01-18 1:49 ` Bart Schaefer
2014-01-18 9:11 ` Axel Beckert
2014-01-19 19:10 ` Peter Stephenson
2014-01-19 21:35 ` Bart Schaefer [this message]
2014-01-19 22:13 ` Simon Ruderich
2014-01-20 0:02 ` Bart Schaefer
2014-01-20 1:10 ` Bart Schaefer
2014-01-20 1:44 ` Bart Schaefer
2014-01-20 3:20 ` Bart Schaefer
2014-02-24 14:38 ` Oliver Kiddle
2014-02-24 15:38 ` Bart Schaefer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=140119133550.ZM5354@torch.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=zsh-workers@zsh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).