Zsh Mailing List Archive
Messages sorted by:
Re: Crash when capturing command output in completion
- X-seq: zsh-workers 34295
- From: Vin Shelton <acs@xxxxxxxxxxxxxxxxxxxx>
- To: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- Subject: Re: Crash when capturing command output in completion
- Date: Thu, 15 Jan 2015 18:53:40 -0500
- Cc: "Zsh Hackers' List" <zsh-workers@xxxxxxx>
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=HgysTjaJo1QvdubmFoxW1MUxoWgCTAjPqAGi8IRdelE=; b=t2yhlLwkL9IzMxdZ08A0MG9QQqh6pt0h4a9xNUzPBpX1zABgRCIa3JoyKB2w+HXovO IPgaxCWGcK/uSLk93jZ0NbKUykSY5yTrPYu4X1dToIDjLd5pl4XAp9DrwuTf3BniLK3u rBdeBvU1mqKWJu52Rtfm+eCWTZAfMzIMhPO1x/8BBvfQgndM0KRB6KMrOIvrna0SAqYG X71Dkzs30y8m/o3zWE5sYDOmLy+fVz/musccDUp15BJKF0W7MmAfZm7oB5eAyuxKjDgM SKhfVHzv780V+cndUi85Ns7ZrVOj4+HoOs4lSSE0+wef2tm3/K78KYErtDY7HwlshJm7 g6hg==
- In-reply-to: <150115135356.ZM23582@torch.brasslantern.com>
- List-help: <mailto:email@example.com>
- List-id: Zsh Workers List <zsh-workers.zsh.org>
- List-post: <mailto:firstname.lastname@example.org>
- Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
- References: <CACeGjnVCkMZrh4iyAqLeuqPbHE+htd=PRNV10UD8kOry7La_TQ@mail.gmail.com> <150115135356.ZM23582@torch.brasslantern.com>
- Sender: ethersoft@xxxxxxxxx
Hey, Bart -
On Thu, Jan 15, 2015 at 4:53 PM, Bart Schaefer
> 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.
I don't know what the auto-fu plugin is. :-)
I will try not to be offended by your accusing me of using oh-my-zsh,
but I will point out that I am not. And if I ever visited the site, I
didn't inhale (to misquote former President Clinton).
> 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.
That's a very useful observation. I will see if I can make any
headway on debugging.
Messages sorted by: