From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-34293-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 22085 invoked by alias); 15 Jan 2015 21:54:33 -0000
Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
X-No-Archive: yes
List-Id: Zsh Workers List <zsh-workers.zsh.org>
List-Post: <mailto:zsh-workers@zsh.org>
List-Help: <mailto:zsh-workers-help@zsh.org>
X-Seq: 34293
Received: (qmail 16314 invoked from network); 15 Jan 2015 21:54:30 -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=PYxIXZlY c=1 sm=1 tr=0	a=FT8er97JFeGWzr5TCOCO5w==:117
 a=kj9zAlcOel0A:10 a=q2GGsy2AAAAA:8	a=oR5dmqMzAAAA:8 a=-9mUelKeXuEA:10
 a=YNv0rlydsVwA:10	a=LVXdtflygqAXQ37FXKUA:9 a=CjuIK1q_8ugA:10
From: Bart Schaefer <schaefer@brasslantern.com>
Message-id: <150115135356.ZM23582@torch.brasslantern.com>
Date: Thu, 15 Jan 2015 13:53:56 -0800
In-reply-to:
 <CACeGjnVCkMZrh4iyAqLeuqPbHE+htd=PRNV10UD8kOry7La_TQ@mail.gmail.com>
Comments: In reply to Vin Shelton <acs@alumni.princeton.edu>
 "Crash when capturing command output in completion" (Jan 15,  2:34pm)
References: <CACeGjnVCkMZrh4iyAqLeuqPbHE+htd=PRNV10UD8kOry7La_TQ@mail.gmail.com>
X-Mailer: OpenZMail Classic (0.9.2 24April2005)
To: "Zsh Hackers' List" <zsh-workers@zsh.org>
Subject: Re: Crash when capturing command output in completion
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii

On Jan 15,  2:34pm, Vin Shelton wrote:
}
} #10 0x00007fa9311a86d6 in zlecore () at zle_main.c:1066
} #11 0x00007fa9311a9060 in zleread (lp=0x6dbcf0 <prompt>, rp=0x0,
} flags=3, context=0,
}     init=0x7fa9311cf14d "zle-line-init", finish=0x7fa9311cf13d
} "zle-line-finish")
}     at zle_main.c:1253

So I suspect you're using something like the auto-fu plugin or OhMyZsh,
because you have recursively entered ZLE from zle-line-init.

We have had other crashes with this configuration, but a stack trace is
not really helpful because typically there will have been a pointer or
counter error somewhere down the stack which causes a crash as the
stack is unwound, so the trace doesn't show the origin of the issue.
We need a run under valgrind or some similar memory debugger.

Here it looks like something has gone wrong with zlemetaline and/or the
calculation of where in the line the right-paren of $( ) appears.