vim.basic crashed with SIGSEGV

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

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

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.

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.