tcsh crashed with SIGSEGV when TAB key is pressed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tcsh (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
tcsh 6.18.01-05 amd64 seems to always crash whenever TAB key is pressed. A sampling from kern.log:
traps: tcsh[13289] general protection ip:7fb2266c4268 sp:7ffde4c57160 error:0 in libc-2.
traps: tcsh[13731] general protection ip:7f0540726268 sp:7ffc0cdf8860 error:0 in libc-2.
traps: tcsh[22613] general protection ip:7fb133804268 sp:7ffc0c3ffd00 error:0 in libc-2.
This is from a Ubuntu MATE 16.10 Alpha 2 AMD64 ISO install to a Macbook Pro Retina (MacBookPro11,1), which was then updated with "aptitude safe-upgrade". (But note that safe-upgrade did not touch the installed tcsh version.)
bash doesn't experience this "crashing with TAB key" behavior, just tcsh. And oddly, this didn't happen immediately after the install, but soon thereafter. And this occurs without a ~/.tcshrc file present in the home directory.
Thanks,
Dan
ProblemType: Crash
DistroRelease: Ubuntu 16.10
Package: tcsh 6.18.01-5
ProcVersionSign
Uname: Linux 4.8.0-16-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
CurrentDesktop: MATE
Date: Sat Sep 24 16:15:52 2016
Dependencies:
gcc-6-base 6.2.0-3ubuntu15
libc6 2.24-0ubuntu1
libgcc1 1:6.2.0-3ubuntu15
libtinfo5 6.0+20160625-
ExecutablePath: /usr/bin/tcsh
InstallationDate: Installed on 2016-09-21 (3 days ago)
InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Alpha amd64 (20160727.1)
ProcCmdline: -csh
Signal: 11
SourcePackage: tcsh
StacktraceTop:
__GI___rewinddir (dirp=0x1847808) at ../sysdeps/
?? ()
?? ()
?? ()
?? ()
Title: tcsh crashed with SIGSEGV in __GI___rewinddir()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1618803, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.