From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13386 invoked by alias); 18 Jan 2014 01:49:31 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Seq: 32277 Received: (qmail 6453 invoked from network); 18 Jan 2014 01:49:16 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2 From: Bart Schaefer Message-id: <140117174902.ZM7366@torch.brasslantern.com> Date: Fri, 17 Jan 2014 17:49:02 -0800 In-reply-to: <20140118002033.GY27889@sym.noone.org> Comments: In reply to Axel Beckert "segfault with exceedingly long path" (Jan 18, 1:20am) References: <20140118002033.GY27889@sym.noone.org> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: zsh-workers@zsh.org Subject: Re: segfault with exceedingly long path MIME-version: 1.0 Content-type: text/plain; charset=us-ascii 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.