From: Axel Beckert <abe@deuxchevaux.org>
To: zsh-workers@zsh.org
Subject: Re: Segfault on "task <Tab><Tab>" with zsh 5.0.2 (minimal dataset to reproduce the issue found)
Date: Tue, 17 Sep 2013 18:10:59 +0200 [thread overview]
Message-ID: <20130917161058.GJ3544@sym.noone.org> (raw)
In-Reply-To: <20130917095657.4cb4ccbf@pwslap01u.europe.root.pri>
Hi,
On Tue, Sep 17, 2013 at 09:56:57AM +0100, Peter Stephenson wrote:
> It's not worth sending these unless they actually provide a way of
> making the crash easily reproducible, in which case please repost that
> information here.
Granted.
I tried to get a reproducible data set and it took me a while to find
that TaskWarrior feature which causes the segfault: Annotations!
Here's how to reproduce the segfault:
abe@kiva6 % zsh -f
kiva6% autoload -Uz compinit
kiva6% compinit
kiva6% task
A configuration file could not be found in
Would you like a sample /home/abe/.taskrc created, so taskwarrior can proceed? (yes/no) yes
[task next]
No matches.
kiva6% task add foo
Created task 1.
kiva6% task 1 annotate bar
Annotating task 1 'foo'.
Annotated 1 task.
kiva6% task [1] 4340 segmentation fault (core dumped) zsh -f
abe@kiva6 %
I built a tiny tar ball containing the resulting data files (and
generated config file), so to reproduce the issue, it should be
sufficient to have the following:
* The attached task-tab-completion-segfaults-zsh.tgz extracted into
$HOME:
drwxr-xr-x abe/tar 0 2013-09-17 17:18 .task/
-rw-r--r-- abe/tar 402 2013-09-17 17:18 .task/undo.data
-rw-r--r-- abe/tar 150 2013-09-17 17:18 .task/pending.data
-rw-r--r-- abe/tar 0 2013-09-17 17:18 .task/completed.data
-rw-r--r-- abe/tar 1129 2013-09-17 17:18 .taskrc
* A recently compiled zsh 5.0.2 (probably with gcc 4.8).
* TaskWarrior 2.2.0 (e.g. from
http://taskwarrior.org/projects/taskwarrior/wiki/Download --
Distribution's package name is often still just "task" which was
TaskWarrior's old name)
* The _task tab-completion file from the source tar-ball (see
http://sources.debian.net/src/task/2.2.0-3/scripts/zsh/_task to just
have a look) at some place where zsh looks for completions.
* Enter "task <Tab><Tab>" into a zsh.
> It might produce some sort of hint using "^X?" instead of the second
> tab.
Nothing, not even a newline or change of the cursor position.
Interestingly the next time, I tried it in the same shell, it
segfaulted on the _first_ Tab key-press.
I used ^U and an empty enter inbetween. At least I could reproduce it
that way multiple times.
Kind regards, Axel
--
/~\ Plain Text Ribbon Campaign | Axel Beckert
\ / Say No to HTML in E-Mail and News | abe@deuxchevaux.org (Mail)
X See http://www.asciiribbon.org/ | abe@noone.org (Mail+Jabber)
/ \ I love long mails: http://email.is-not-s.ms/ | http://noone.org/abe/ (Web)
next prev parent reply other threads:[~2013-09-17 16:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-12 22:18 Segfault on "task <Tab><Tab>" with zsh 5.0.2 Axel Beckert
2013-09-13 8:37 ` Peter Stephenson
2013-09-13 11:34 ` Axel Beckert
2013-09-13 11:51 ` Peter Stephenson
2013-09-13 12:24 ` Axel Beckert
2013-09-13 12:36 ` Peter Stephenson
2013-09-13 19:33 ` Pierre Schmitz
2013-09-16 16:17 ` Ivan S. Freitas
2013-09-16 17:18 ` Axel Beckert
2013-09-17 8:56 ` Peter Stephenson
2013-09-17 16:10 ` Axel Beckert [this message]
2013-09-17 16:35 ` Segfault on "task <Tab><Tab>" with zsh 5.0.2 (minimal dataset to reproduce the issue found) Axel Beckert
2013-09-17 19:05 ` Peter Stephenson
2013-09-17 20:12 ` Axel Beckert
2013-09-18 3:05 ` Bart Schaefer
2013-09-18 21:50 ` Segfault on "task <Tab><Tab>" with zsh 5.0.2 [PATCH] Axel Beckert
2013-09-19 8:49 ` Peter Stephenson
2013-09-19 14:42 ` 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=20130917161058.GJ3544@sym.noone.org \
--to=abe@deuxchevaux.org \
--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).