From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13745 invoked by alias); 14 Dec 2014 18:42:42 -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: 33966 Received: (qmail 19619 invoked from network); 14 Dec 2014 18:42:41 -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 X-CMAE-Score: 0 X-CMAE-Analysis: v=2.1 cv=Ko/6AtSI c=1 sm=1 tr=0 a=FT8er97JFeGWzr5TCOCO5w==:117 a=kj9zAlcOel0A:10 a=q2GGsy2AAAAA:8 a=oR5dmqMzAAAA:8 a=-9mUelKeXuEA:10 a=A92cGCtB03wA:10 a=chc_v7dKBkFkVpWY8nAA:9 a=CjuIK1q_8ugA:10 From: Bart Schaefer Message-id: <141214104300.ZM23759@torch.brasslantern.com> Date: Sun, 14 Dec 2014 10:43:00 -0800 In-reply-to: <20141214182021.1944bbcd@pws-pc.ntlworld.com> Comments: In reply to Peter Stephenson "Re: Complex config triggering Segfault in pattern matching code." (Dec 14, 6:20pm) References: <141213152840.ZM16632@torch.brasslantern.com> <141213204032.ZM16766@torch.brasslantern.com> <20141214182021.1944bbcd@pws-pc.ntlworld.com> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: zsh-workers@zsh.org Subject: Re: Complex config triggering Segfault in pattern matching code. MIME-version: 1.0 Content-type: text/plain; charset=us-ascii On Dec 14, 6:20pm, Peter Stephenson wrote: } } Bart Schaefer wrote: } > #280 recursiveedit (args=0x7fb1f7f4ba70) at zle_main.c:181 } > } > So at this point we haven't even finished initializing ZLE yet, but one of } > these "auto-fu" functions has recursively invoked it. This is a recipe for } > disaster if ever I saw one. } } After zle-line-init runs (in zleread),the next thing we do is zrefresh() } and then zlecore(). So I think it *has* finished initialising --- } zrefresh() and zlecore() are the stuff that we can only do when zsh is } set up and we can do them at this point. OK; that is after all why I invoked you ... (turn three times counter- clockwise, then fling salt over your right shoulder and ...) } > #126 completecall (args=0x7fb1f7f38918) at zle_tricky.c:208 } } This is utterly bizarre, but, again, I'm not really sure what the core } shell should be disallowing. It's up to the user rather than the shell } not to complete anything before they've even started up the command } line... After thinking about this, it occurred to me that we're inside recursive- edit, so probably the stack has grown and shrunk several times as input was typed before we got the trace that led to this particular error. So the buffer likely wasn't empty after all.