Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Crash when capturing command output in completion
- X-seq: zsh-workers 34293
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: "Zsh Hackers' List" <zsh-workers@xxxxxxx>
- Subject: Re: Crash when capturing command output in completion
- Date: Thu, 15 Jan 2015 13:53:56 -0800
- In-reply-to: <CACeGjnVCkMZrh4iyAqLeuqPbHE+htd=PRNV10UD8kOry7La_TQ@mail.gmail.com>
- List-help: <mailto:zsh-workers-help@zsh.org>
- List-id: Zsh Workers List <zsh-workers.zsh.org>
- List-post: <mailto:zsh-workers@zsh.org>
- Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
- References: <CACeGjnVCkMZrh4iyAqLeuqPbHE+htd=PRNV10UD8kOry7La_TQ@mail.gmail.com>
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.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author