From: Peter Stephenson <p.stephenson@samsung.com>
To: Bjorn Baron <bjornbaron@outlook.com>,
"zsh-workers@zsh.org" <zsh-workers@zsh.org>
Subject: Re: BUG: Zsh crashes
Date: Fri, 13 Jan 2017 17:52:42 +0000 [thread overview]
Message-ID: <20170113175242.16210658@pwslap01u.europe.root.pri> (raw)
In-Reply-To: <DB6PR1001MB10324259D98A08DA4938F0E6D7780@DB6PR1001MB1032.EURPRD10.PROD.OUTLOOK.COM>
On Fri, 13 Jan 2017 17:40:48 +0000
Bjorn Baron <bjornbaron@outlook.com> wrote:
> Dear zsh developers,
>
> I have found a bug in zsh. You can crash zsh with for example a
> segmentation fault by autocompleting `rustc --pretty flowgraph` two times
>
> # Reproduction:
> type `rustc --pretty flowgraph`
> press tab 2x
>
> # Actual result:
> Zsh crashes.
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.
pws
next prev parent reply other threads:[~2017-01-13 17:52 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 [this message]
2017-01-14 1:09 ` Phil Pennock
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=20170113175242.16210658@pwslap01u.europe.root.pri \
--to=p.stephenson@samsung.com \
--cc=bjornbaron@outlook.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).