From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7079 invoked by alias); 26 Oct 2015 07:19:00 -0000 Mailing-List: contact zsh-users-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Users List List-Post: List-Help: X-Seq: 20824 Received: (qmail 8292 invoked from network); 26 Oct 2015 07:18:56 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,T_DKIM_INVALID autolearn=ham autolearn_force=no version=3.4.0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:references:user-agent:from:to:subject:in-reply-to:date :message-id:mime-version:content-type; bh=CYF8KSF5r49nrdo+Ed/V0PN7zzu8GNEqmKmwTQpyASk=; b=0y1JdEsK2hJPsGp7WJiqJUWUIeRjYsVdJ9aMe3qazqyt4SwJZn4N162qhQEEDzuD3T wEr+rEiwUyi1g0XrYBk96iQqoES23T9mjo4+FqLXSekNEgjDXGXC9dO+SGC5oZFb9e5g GZ+NexmMxTupflP2SSFiof1Ik7gi5L1W2GxKPohpqnTB5hfUH6PhfFye4RxFEekJg+1s uHS0BZIcAwWAfnc+ZSucyIjqzrBGrlxoE9cCLUHIcCKc6KOKWW9iAy2XTIg45ZrF9AA7 L+LGC6LrEthpRdWU9tR0OqF6a7ifA2AwUCibU0kIJZfFHc20BxQLsHNGtts4gkK9AoZP D/7w== X-Received: by 10.112.171.10 with SMTP id aq10mr15804394lbc.85.1445843932830; Mon, 26 Oct 2015 00:18:52 -0700 (PDT) Sender: "diggler@gmail.com" References: <874mhfe8ng.fsf@djcbsoftware.nl> <151025095136.ZM29675@torch.brasslantern.com> <87y4eqahet.fsf@djcbsoftware.nl> <151025180706.ZM30568@torch.brasslantern.com> User-agent: mu4e 0.9.15; emacs 25.0.50.125 From: Dirk-Jan C. Binnema To: zsh-users@zsh.org Subject: Re: segfault in mkundoent when completing In-reply-to: <151025180706.ZM30568@torch.brasslantern.com> Date: Mon, 26 Oct 2015 09:18:50 +0200 Message-ID: <87fv0ym71h.fsf@djcbsoftware.nl> MIME-Version: 1.0 Content-Type: text/plain On Monday Oct 26 2015, Bart Schaefer wrote: > On Oct 25, 9:15pm, Dirk-Jan C. Binnema wrote: > } > } It seems to happen in all directories; I suspect it's something specific > } to my configuration (when not using my ~/.zshrc, there's no crash), > } though I don't think there's anything special there (and it worked fine > } for years before the mentioned commit). > > Whether it "worked fine for years before" or not, probably the only way > anyone else will be able to track this down is if you first narrow down > the setting(s) from your .zshrc that must be in place in order to trigger > the error. Hmmm, it seems some kind of interaction between a few different things; but I was amble to reproduce it with this ~/.zshrc (using the external highlighting package): --8<---------------cut here---------------start------------->8--- setopt allexport autoload -U compinit compinit source ~/Sources/zsh-syntax-highlighting/zsh-syntax-highlighting.zsh --8<---------------cut here---------------end--------------->8--- Kind regards, Dirk. -- Dirk-Jan C. Binnema Helsinki, Finland e:djcb@djcbsoftware.nl w:www.djcbsoftware.nl pgp: D09C E664 897D 7D39 5047 A178 E96A C7A1 017D DA3C