From: Vin Shelton <acs@alumni.princeton.edu>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: "Zsh Hackers' List" <zsh-workers@zsh.org>
Subject: Re: Crash when capturing command output in completion
Date: Thu, 15 Jan 2015 18:53:40 -0500 [thread overview]
Message-ID: <CACeGjnVwLgogjoWwCMOk4d-5R+4QOeishx+kYfV0dfE4RS_L6g@mail.gmail.com> (raw)
In-Reply-To: <150115135356.ZM23582@torch.brasslantern.com>
Hey, Bart -
On Thu, Jan 15, 2015 at 4:53 PM, Bart Schaefer
<schaefer@brasslantern.com> wrote:
> 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.
- Vin
next prev parent reply other threads:[~2015-01-15 23:53 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-15 19:34 Vin Shelton
2015-01-15 21:53 ` Bart Schaefer
2015-01-15 23:53 ` Vin Shelton [this message]
2015-01-16 0:27 ` Bart Schaefer
2015-01-16 3:11 ` Vin Shelton
2015-01-16 3:17 ` Vin Shelton
2015-01-16 4:43 ` Bart Schaefer
2015-01-16 5:20 ` Bart Schaefer
2015-01-16 9:44 ` Peter Stephenson
2015-01-16 12:57 ` Peter Stephenson
2015-01-16 16:18 ` Bart Schaefer
2015-01-16 16:25 ` Bart Schaefer
2015-01-16 18:04 ` Peter Stephenson
2015-01-16 18:58 ` Bart Schaefer
2015-01-16 19:16 ` Bart Schaefer
2015-01-16 20:05 ` Peter Stephenson
2015-01-16 19:19 ` Ray Andrews
2015-01-16 6:43 ` Ray Andrews
2015-01-16 7:49 ` Bart Schaefer
2015-01-16 16:21 ` Ray Andrews
2015-01-16 16:34 ` Bart Schaefer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CACeGjnVwLgogjoWwCMOk4d-5R+4QOeishx+kYfV0dfE4RS_L6g@mail.gmail.com \
--to=acs@alumni.princeton.edu \
--cc=schaefer@brasslantern.com \
--cc=zsh-workers@zsh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).