When using vim, exiting the program logs an error to the screen. Reproducible: Always Steps to Reproduce: 1. vim anyfile 2. exit (:q) Actual Results: Vim: Caught deadly signal SEGV Vim: Finished. Segmentation fault Expected Results: no errors vim version: app-editors/vim-6.3-r2 emerge info: Portage 2.0.51.19 (default-linux/ppc64/2005.0, gcc-3.4.4, glibc-2.3.4.20041102-r1, 2.6.11-gentoo-r8 ppc64) ================================================================= System uname: 2.6.11-gentoo-r8 ppc64 POWER3 (630) Gentoo Base System version 1.6.12 Python: dev-lang/python-2.3.5 [2.3.5 (#1, Jul 5 2005, 03:38:28)] dev-lang/python: 2.3.5 sys-apps/sandbox: [Not Present] sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.9.5, 1.5, 1.8.5-r3, 1.7.9-r1, 1.6.3, 1.4_p6 sys-devel/binutils: 2.15.90.0.3-r5 sys-devel/libtool: 1.5.18-r1 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="ppc64" AUTOCLEAN="yes" CFLAGS="-O2 -pipe -mcpu=power3" CHOST="powerpc64-unknown-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -pipe -mcpu=power3" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="ppc64 berkdb bitmap-fonts emboss fortran gif gpm jpeg ncurses pam perl pngpython readline ssl tcpd truetype truetype-fonts type1-fonts unicode zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTDIR_OVERLAY
Similar behavior seen in bug 69453 (though it is a gvim bug)
I upgraded to 6.3.075, and I still see the error.
Also saw the following error while moving back to the previous version (6.3-r2) of vim, not sure if it is related: <...> --- !targe sym /usr/bin/ex * Updating documentation tags in /usr/share/vim/vim63 /usr/portage/eclass/vim-doc.eclass: line 37: 3193 Segmentation fault DISPLAY= $vim -u NONE -U NONE -T xterm -X -n -f '+set nobackup nomore' "+helptags $d/doc" '+qa!' </dev/null >&/dev/null >>> Regenerating /etc/ld.so.cache... * Caching service dependencies ... [ ok ] >>> Regenerating /etc/ld.so.cache... * Caching service dependencies ... [ ok ] >>> Auto-cleaning packages ... >>> No outdated packages were found on your system.
this is a known problem as a _workaround_ is to compile vim without perl support: echo "app-editors/vim -perl" >> /etc/portage/package.use && emerge vim Also I found out that the combination of gcc-4.0.1_pre20050702, glibc-2.3.5.20050421, binutils-2.16.1 and vim-6.3.068 solves this problem. (maybe only a newer gcc version is needed, but this are the versions, which I used)
the first sentence is somehow wired... this is what I wanted to say: this is a known problem. A _workaround_ is to compile vim without perl support:
I updated glibc, binutils, and vim, and I still see the problem. The solution might be in gcc 4.0, but that would only be a work around. From comment #4, if this is a know issue, is there a bug I should dupe this one to?
(In reply to comment #6) > From comment #4, if this is a know issue, is there a bug I should dupe this one to? It is known as in "someone (IIRC dostrow) is looking into this, when he has some spare time".
Is this bug still present in current versions of vim or can this bug be closed out?
this bug is still present and the workaround is to add "app-editors/vim -perl" to /etc/portage/package.keywords. this bug will be solved when >=gcc-4.0 will be stable on ppc64. (this might not happen within the next months...)
closing this bug as gcc 4.1.1 with glibc 2.4 is now stable and this bug disappears as a result.
stick a fork in it!
