Zsh Mailing List Archive
Messages sorted by:
Re: BUG: Zsh crashes
- X-seq: zsh-workers 40354
- From: Phil Pennock <zsh-workers+phil.pennock@xxxxxxxxxxxx>
- To: Peter Stephenson <p.stephenson@xxxxxxxxxxx>
- Subject: Re: BUG: Zsh crashes
- Date: Sat, 14 Jan 2017 01:09:00 +0000
- Cc: Bjorn Baron <bjornbaron@xxxxxxxxxxx>, "zsh-workers@xxxxxxx" <zsh-workers@xxxxxxx>
- Dkim-signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=spodhuis.org; s=d201611; h=In-Reply-To:Content-Type:MIME-Version:References :Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To:Content-Transfer-Encoding :Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=wq6gk0WzdyyN2G9l/iO1Fx7MfjwbpeBZ8mtRICEb9gM=; b=xjsk1sbOkvVm/wYESeQumTHUyI rATOdipDQ+nNfaDi8HbQJDx76hMBfbRTfY6ZLp33bFJ7zdDrOv9IBbSKOHMkkjh/nB0RvE7jBwM0r 6mzUVQAB22lX/52vznK5skztloH7PLD9HHxEbLv5Ig8SJmMqvtTbKQubynxjReAGT5LxI3eUmMfWb d6MGIYYgHXwKg/5CWrpRvPFIZELQ;
- In-reply-to: <firstname.lastname@example.org>
- 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
- Openpgp: url=https://www.security.spodhuis.org/PGP/keys/0x4D1E900E14C1CC04.asc
- References: <CGME20170113174208epcas1p109452434d2f95e52b24e49029ce15943@epcas1p1.samsung.com> <DB6PR1001MB10324259D98A08DA4938F0E6D7780@DB6PR1001MB1032.EURPRD10.PROD.OUTLOOK.COM> <email@example.com>
On 2017-01-13 at 17:52 +0000, Peter Stephenson wrote:
> You always need to report both the zsh version and, in the case of
> completion crashes, how this is set up (looks like in your case this is
> down to oh-my-zsh so I guess you don't have explicit details of your
> own setup beyond that).
> However, you appear to be using zsh 5.0.2, if I've read you're
> web report correctly --- that's several years out of date, so I'm
> afraid you're not going to get any direct help with the version you're
> Obviously, if it still happens with 5.3.1 that's a different matter.
It does. Disclaimer: my oh-my-zsh experience is limited to having
helped former co-workers with their setups and writing a custom theme
for one who wanted some special employer-specific stuff in their prompt.
uname .. => Darwin 16.3.0 (it's MacOS 10.12.2)
zsh installed via brew, installed as a binary package ("bottle"), the
./configure flags can be seen in:
...% env - /usr/local/bin/zsh -f
tungsten% export TERM=xterm-256color; LC_CTYPE=en_US.UTF-8
tungsten% echo $ZSH_VERSION
tungsten% export ZSH=$HOME/.oh-my-zsh; ZSH_THEME="agnoster"; COMPLETION_WAITING_DOTS="true"
tungsten% plugins=(git rust)
tungsten% . $ZSH/oh-my-zsh.sh
This with having freshly cloned github.com:robbyrussell/oh-my-zsh.git to
~/.oh-my-zsh and no modifications locally; checked out at 0b4bba4c
No install steps for oh-my-zsh or curl|sh stuff done, it's purely a git
repo clone to that path.
...% rustc --pretty flowgraph==......zsh(41997,0x7fffdf23d3c0) malloc: ***
error for object 0x7fc75560ef60: pointer being freed was not allocated
*** set a breakpoint in malloc_error_break to debug
zsh: abort (core dumped) env - /usr/local/bin/zsh -f
% lldb -c /cores/core.41997 /usr/local/bin/zsh
(lldb) target create "/usr/local/bin/zsh" --core "/cores/core.41997"
warning: (x86_64) /cores/core.41997 load command 386 LC_SEGMENT_64 has a fileoff + filesize (0x2d3ae000) that extends beyond the end of the file (0x2d3ad000), the segment will be truncated to match
warning: (x86_64) /cores/core.41997 load command 387 LC_SEGMENT_64 has a fileoff (0x2d3ae000) that extends beyond the end of the file (0x2d3ad000), ignoring this section
Core file '/cores/core.41997' (x86_64) was loaded.
I've put the output of `bt` into:
That URL does not require authentication to access, no GitHub account
needed, it's just a convenient paste-site. There are 207 frames, which
is a little long for this email.
My lldb-fu is even weaker than my remnants of gdb-fu. Not sure what's
useful to drill further. My zsh allocator internals knowledge is almost
two decades rusty at this point.
Hopefully the above reproduction steps will help others.
Messages sorted by: