zsh: segmentation fault (core dumped) sudo -i

Bug #1634488 reported by Hadmut Danisch
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
zsh (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Hi,

since I've upgraded from 16.04 to 16.10, the zsh crashes quite often with a segmentation fault.

I've noticed that this occurs not always, but if, then always in these two cases:

- calling ls (in my case an alias for ls -F and thus the internal ls function)

- using file name completion

which both are related to opening directories and reading their contents. I've done a strace, which seems to confirm this (crashing within ls):

...

6781 open(".", O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC) = 3
6781 fstat(3, {st_mode=S_IFDIR|0700, st_size=806, ...}) = 0
6781 lseek(3, 0, SEEK_SET) = 0
6781 --- SIGSEGV {si_signo=SIGSEGV, si_code=SI_KERNEL, si_addr=0} ---
6781 +++ killed by SIGSEGV (core dumped) +++

which again implies problems pretty close to opening directories.

regards

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: zsh 5.2-5ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21
Uname: Linux 4.4.0-43-generic x86_64
NonfreeKernelModules: zunicode zcommon znvpair zavl
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: XFCE
Date: Tue Oct 18 14:31:18 2016
InstallationDate: Installed on 2016-04-22 (178 days ago)
InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420)
SourcePackage: zsh
UpgradeStatus: Upgraded to yakkety on 2016-10-17 (1 days ago)

Revision history for this message
Hadmut Danisch (hadmut) wrote :
Revision history for this message
Hadmut Danisch (hadmut) wrote :

Sorry, I've made a mistake. The bug occured with the tcsh, not the zsh. A usermod to set the shell to zsh had failed, and the bug message mentioning zsh came from the outer zsh (from where sudo was run), that's why I believed a zsh had crashed.

Changed in zsh (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.