From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: segfault with exceedingly long path
Date: Fri, 17 Jan 2014 17:49:02 -0800 [thread overview]
Message-ID: <140117174902.ZM7366@torch.brasslantern.com> (raw)
In-Reply-To: <20140118002033.GY27889@sym.noone.org>
On Jan 18, 1:20am, Axel Beckert wrote:
}
} this is a forward of http://bugs.debian.org/418199
This is a known issue and unlikely ever to be fixed. Various parts
of the shell rely on system limits such as PATH_MAX which cannot be
dynamically changed. There's a comment with some explanation around
lines 109-137 of Src/compat.c.
The upshot is that if you try hard enough you can always create a path
that will exceed some limit or other.
next prev parent reply other threads:[~2014-01-18 1:49 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 [this message]
2014-01-18 9:11 ` Axel Beckert
2014-01-19 19:10 ` Peter Stephenson
2014-01-19 21:35 ` Bart Schaefer
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=140117174902.ZM7366@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).