From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1478 invoked by alias); 7 Jul 2014 01:12:14 -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: 32851 Received: (qmail 20779 invoked from network); 7 Jul 2014 01:12:10 -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=-0.4 required=5.0 tests=BAYES_00,FAKE_REPLY_C autolearn=ham version=3.3.2 Date: Mon, 7 Jul 2014 03:12:06 +0200 From: Vincent Lefevre To: zsh-workers@zsh.org Subject: Re: segmentation fault with {1..1234567} Message-ID: <20140707011206.GA3168@xvii.vinc17.org> Mail-Followup-To: zsh-workers@zsh.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <140706091609.ZM18865@torch.brasslantern.com> <140706124600.ZM19572@torch.brasslantern.com> X-Mailer-Info: http://www.vinc17.net/mutt/ User-Agent: Mutt/1.5.21-6305-vl-r59709 (2013-04-16) On 2014-07-06 12:46:00 -0700, Bart Schaefer wrote: > On Jul 6, 2:09am, Vincent Lefevre wrote: > } > } I've reported the bug on the Debian BTS: > } > } https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753906 > > Does that actually help? Will they fix it without an upstream patch? Since you couldn't reproduce the problem, it could have been dependent on configure options (another problem is that zsh doesn't have a BTS, so that it becomes difficult to track bugs). On 2014-07-06 09:16:09 -0700, Bart Schaefer wrote: > On Jul 6, 1:39am, Vincent Lefevre wrote: > } Subject: Re: segmentation fault with {1..1234567} > } > } On 2014-07-05 09:57:03 -0700, Bart Schaefer wrote: > } > > } > Then it's probably a per-process resource limit problem. > } > } No, I don't have any per-process limitation on the memory. > > Apparently, though, you may have one on stack space. There is always a limit. Since it is not possible to detect allocation failures for the stack, it means that to avoid random crashes, processes should pre-allocate memory there and be written in such a way that they don't use more than pre-allocated. The pre-allocated memory should not be too small, but should not be too large either, otherwise the memory will be exhausted too easily. So, the 8MB default limit for GNU/Linux is very reasonable, in particular taking into account the fact that a small part is pre-allocated. -- Vincent Lefèvre - Web: 100% accessible validated (X)HTML - Blog: Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)