Bug 1380499

Summary: [abrt] zsh: execcmd(): zsh killed by SIGSEGV
Product: [Fedora] Fedora Reporter: iakovos Gurulian <jack.gurulian>
Component: zshAssignee: Kamil Dudka <kdudka>
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 24CC: dmaphy, jack.gurulian, james.antill, j, kdudka, svashisht
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/7d5ea282be347b301d393c45947288d299f1fe18
Whiteboard: abrt_hash:0b5b3d5b4271c069b1554c03887ed0b7ea4e3d2a;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-09-30 10:55:26 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: mountinfo
none
File: namespaces
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description iakovos Gurulian 2016-09-29 18:58:42 UTC 
Description of problem:
I typed "cd -" and enter and the terminal crashed

Version-Release number of selected component:
zsh-5.2-5.fc24

Additional info:
reporter:       libreport-2.7.2
backtrace_rating: 4
cmdline:        zsh
crash_function: execcmd
executable:     /usr/bin/zsh
global_pid:     4675
kernel:         4.7.4-200.fc24.x86_64
pkg_fingerprint: 73BD E983 81B4 6521
pkg_vendor:     Fedora Project
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 execcmd at exec.c:2461
 #1 execpline2 at exec.c:1748
 #2 execpline at exec.c:1526
 #3 execlist at exec.c:1284
 #4 execif at loop.c:549
 #5 execcmd at exec.c:3474
 #6 execpline2 at exec.c:1748
 #7 execpline at exec.c:1526
 #8 execlist at exec.c:1284
 #9 execode at exec.c:1075
Comment 1 iakovos Gurulian 2016-09-29 18:59:20 UTC 
Created attachment 1206007 [details]
File: backtrace
Comment 2 iakovos Gurulian 2016-09-29 18:59:22 UTC 
Created attachment 1206008 [details]
File: cgroup
Comment 3 iakovos Gurulian 2016-09-29 18:59:26 UTC 
Created attachment 1206009 [details]
File: core_backtrace
Comment 4 iakovos Gurulian 2016-09-29 18:59:27 UTC 
Created attachment 1206010 [details]
File: dso_list
Comment 5 iakovos Gurulian 2016-09-29 18:59:29 UTC 
Created attachment 1206011 [details]
File: environ
Comment 6 iakovos Gurulian 2016-09-29 18:59:31 UTC 
Created attachment 1206012 [details]
File: exploitable
Comment 7 iakovos Gurulian 2016-09-29 18:59:32 UTC 
Created attachment 1206013 [details]
File: limits
Comment 8 iakovos Gurulian 2016-09-29 18:59:35 UTC 
Created attachment 1206014 [details]
File: maps
Comment 9 iakovos Gurulian 2016-09-29 18:59:36 UTC 
Created attachment 1206015 [details]
File: mountinfo
Comment 10 iakovos Gurulian 2016-09-29 18:59:38 UTC 
Created attachment 1206016 [details]
File: namespaces
Comment 11 iakovos Gurulian 2016-09-29 18:59:39 UTC 
Created attachment 1206017 [details]
File: open_fds
Comment 12 iakovos Gurulian 2016-09-29 18:59:41 UTC 
Created attachment 1206018 [details]
File: proc_pid_status
Comment 13 iakovos Gurulian 2016-09-29 18:59:43 UTC 
Created attachment 1206019 [details]
File: var_log_messages
Comment 14 Kamil Dudka 2016-09-30 10:25:20 UTC 
Looks like stack overflow due to unbounded recursive call.  Is it reproducible?  Are any extensions or locally sourced scripts needed to trigger the crash?
Comment 15 iakovos Gurulian 2016-09-30 10:34:19 UTC 
(In reply to Kamil Dudka from comment #14)
> Looks like stack overflow due to unbounded recursive call.  Is it
> reproducible?  Are any extensions or locally sourced scripts needed to
> trigger the crash?

I had changed the theme in .zshrc before it happened, and sourced it. I will try to reproduce it and report back.
Comment 16 iakovos Gurulian 2016-09-30 10:48:07 UTC 
Yes it is reproducible. Steps:

1. run 'source .zshrc'
2. run 'cd<space>'
3. crash

It doesn't look like a ZSH bug though. It only occurs when I have the zsh-syntax-highlighting plugin on. I will report it there.
Comment 17 Kamil Dudka 2016-09-30 10:51:54 UTC 
Thanks for the additional info!  Please close this bug once the hypotheses is confirmed.
Comment 18 iakovos Gurulian 2016-09-30 10:55:26 UTC 
It is in the known issues list, when using zsh-autosuggestions and zsh-syntax-highlighting. More info here: https://github.com/zsh-users/zsh-syntax-highlighting/issues/353

Closing.