From: Phil Pennock <zsh-workers+phil.pennock@spodhuis.org>
To: Peter Stephenson <p.stephenson@samsung.com>
Cc: Bjorn Baron <bjornbaron@outlook.com>,
"zsh-workers@zsh.org" <zsh-workers@zsh.org>
Subject: Re: BUG: Zsh crashes
Date: Sat, 14 Jan 2017 01:09:00 +0000 [thread overview]
Message-ID: <20170114010859.GA22474@tower.spodhuis.org> (raw)
In-Reply-To: <20170113175242.16210658@pwslap01u.europe.root.pri>
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
> using...
>
> 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:
https://github.com/Homebrew/homebrew-core/blob/master/Formula/zsh.rb
...% env - /usr/local/bin/zsh -f
tungsten% export TERM=xterm-256color; LC_CTYPE=en_US.UTF-8
tungsten% echo $ZSH_VERSION
5.3.1
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.
(lldb)
I've put the output of `bt` into:
https://gist.github.com/philpennock/89531216fb7096c6906e5aa1f0fa8fc7
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.
-Phil
next prev parent reply other threads:[~2017-01-14 1:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20170113174208epcas1p109452434d2f95e52b24e49029ce15943@epcas1p1.samsung.com>
2017-01-13 17:40 ` Bjorn Baron
2017-01-13 17:52 ` Peter Stephenson
2017-01-14 1:09 ` Phil Pennock [this message]
2017-01-14 2:48 ` Daniel Shahaf
2017-01-14 20:19 ` Peter Stephenson
2017-01-14 20:36 ` Peter Stephenson
2017-01-14 22:10 ` Peter Stephenson
2017-01-14 22:12 ` Bart Schaefer
2017-01-15 2:32 ` Daniel Shahaf
2017-01-14 4:08 ` Eric Cook
2017-01-14 4:18 ` Eric Cook
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=20170114010859.GA22474@tower.spodhuis.org \
--to=zsh-workers+phil.pennock@spodhuis.org \
--cc=bjornbaron@outlook.com \
--cc=p.stephenson@samsung.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).