Description of problem: 1. Run ZSH shell 2. Type-in this command and press ENTER perl -e <<EOF$blee = {}; $blee->{fuj} = undef; print $blee->{fuj}, "\n"; print exists $blee->{fuj}, "\n"; delete $blee->{fuj}; print exists $blee->{fuj}, "\n"' 3. The "quote>" prompt appears. Press "Ctrl-C" to interrupt. 4. Normal shell prompt appears. Press ENTER. 5. The "heredoc>" prompt appears. Press "Ctrl-C" to interrupt. 6. ZSH segfaults. Version-Release number of selected component: zsh-5.0.2-1.fc18 Additional info: reporter: libreport-2.1.4 backtrace_rating: 4 cmdline: /bin/zsh crash_function: setheredoc executable: /usr/bin/zsh kernel: 3.9.4-200.fc18.x86_64 runlevel: N 5 uid: 1000 Truncated backtrace: Thread no. 1 (5 frames) #0 setheredoc at parse.c:1946 #1 zshlex at lex.c:421 #2 parse_event at parse.c:451 #3 loop at init.c:132 #4 zsh_main at init.c:1617
Created attachment 759113 [details] File: backtrace
Created attachment 759114 [details] File: cgroup
Created attachment 759115 [details] File: core_backtrace
Created attachment 759116 [details] File: dso_list
Created attachment 759117 [details] File: environ
Created attachment 759118 [details] File: limits
Created attachment 759119 [details] File: maps
Created attachment 759120 [details] File: open_fds
Created attachment 759121 [details] File: proc_pid_status
Created attachment 759122 [details] File: var_log_messages
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
It occurs in Fedora 20 too.
The issue is still reproducible with Zsh 5.0.5. Setting FutureFeature keyword so the issue won't be closed automatically.
proposed upstream: http://www.zsh.org/mla/workers/2015/msg00832.html
upstream commit: http://sourceforge.net/p/zsh/code/ci/2e48eceb
fixed in zsh-5.0.7-7.fc23
zsh-5.0.7-7.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/zsh-5.0.7-7.fc22
zsh-5.0.7-7.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/zsh-5.0.7-7.fc21
zsh-5.0.7-7.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/zsh-5.0.7-7.fc20
zsh-5.0.7-7.fc22 works
(In reply to lnie from comment #20) > zsh-5.0.7-7.fc22 works Thanks for confirmation!
Package zsh-5.0.7-7.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing zsh-5.0.7-7.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-6466/zsh-5.0.7-7.fc20 then log in and leave karma (feedback).
zsh-5.0.7-7.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.
zsh-5.0.7-7.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
zsh-5.0.7-7.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.
(In reply to Kamil Dudka from comment #15) > upstream commit: > > http://sourceforge.net/p/zsh/code/ci/2e48eceb The above upstream commit had (for me) unexpected side effect: http://www.zsh.org/mla/workers/2018/msg01655.html