vim.basic crashed with SIGSEGV

Bug #957793 reported by choury
26
This bug affects 3 people
Affects Status Importance Assigned to Milestone
vim (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

it crashed when i run " vim –version |grep -o ‘+clientserver\|+signs’ "

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: vim 2:7.3.429-2ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9
Uname: Linux 3.2.0-18-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 1.94.1-0ubuntu2
Architecture: amd64
Date: Sat Mar 17 18:01:45 2012
ExecutablePath: /usr/bin/vim.basic
InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64+mac (20120313)
ProcCmdline: vim –version
ProcEnviron:
 SHELL=/bin/bash
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 LANGUAGE=en_US
Signal: 11
SourcePackage: vim
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: vim.basic crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
choury (zhouwei400-w) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 get_func_tv (name=0x103c781 "bufnr('$')", len=5, rettv=0xe4a500, arg=0xe4a4b8, firstline=1, lastline=1, doesrange=0xe4a228, evaluate=1, selfdict=0x0) at eval.c:8177
 eval7 (arg=0xe4a4b8, rettv=0xe4a500, evaluate=1, want_string=<optimized out>) at eval.c:5138
 eval6 (arg=0xe4a4b8, rettv=0xe4a500, evaluate=1, want_string=<optimized out>) at eval.c:4790
 eval5 (arg=0xe4a4b8, rettv=0xe4a500, evaluate=1) at eval.c:4606
 eval4 (evaluate=1, rettv=0xe4a500, arg=0xe4a4b8) at eval.c:4299

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in vim (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
choury (zhouwei400-w)
visibility: private → public
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in vim (Ubuntu):
status: New → Confirmed
tags: added: utopic
Revision history for this message
Bruce Pieterse (octoquad) wrote :

In my case I accidentally used sudo vi /etc/ instead of the full path of the file
sudo vi /etc/asterisk/manager.conf. Vim opened normally, I just exited
straight away with :q, but the crash report only occurred a few hours
later.

History confirms timestamp:
41328* 2015-01-13 14:21 sudo vi /etc/

Vim crashed at roughly 17:01.

Original bug report #1410294.

Revision history for this message
Bruce Pieterse (octoquad) wrote :

On Ubuntu Gnome 15.04, running the original reporters command "vim –version |grep -o ‘+clientserver\|+signs’" causes vim to output "Vim: Warning: Output is not to a terminal" with the terminal window not accepting CTRL+C, but CTRL+Z suspends correctly. Seems like the child process might be preventing it:

[1] + 28277 suspended vim –version |
       28278 suspended grep --color=auto --exclude-dir={.bzr,.cvs,.git,.hg,.svn} -o

You have to kill the process or close the terminal, but it doesn't crash.

Additionally replacing ‘+clientserver\|+signs’ with '+clientserver\|+signs' works normally.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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