Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#29377 - [vim] segfault while loading a cpp file

Attached to Project: Arch Linux
Opened by Vivien Botton (snap) - Tuesday, 10 April 2012, 16:40 GMT
Last edited by Thomas Dziedzic (tomd123) - Saturday, 15 September 2012, 04:07 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Thomas Dziedzic (tomd123)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
I opened the file named 'CompositeMonster.hpp' then I used a :vs command to open 'CompositeMonster.cpp'.
After a few seconds vim segfaulted.
I have attached the two files plus a valgrind output.

Additional info:
gvim 7.3.495-1
I use ctags for coloration.
   CompositeMonster.hpp (0.3 KiB)
   CompositeMonster.cpp (0.3 KiB)
   vim.log (218.8 KiB)
This task depends upon

Closed by  Thomas Dziedzic (tomd123)
Saturday, 15 September 2012, 04:07 GMT
Reason for closing:  Fixed
Additional comments about closing:  bumped vim to 7.3.661
Comment by Thomas Dziedzic (tomd123) - Tuesday, 10 April 2012, 19:56 GMT
Can you reproduce this constantly?
It doesn't segfault after I open those 2.

Please get the stack trace and submit a bug upstream.
Paste the upstream bug report here for reference please.
Comment by Alex Theiakos (alelos) - Wednesday, 11 April 2012, 09:54 GMT
I also have the same problem after the last update. It only happens with C (haven't tried cpp) files for me, after ~30sec I get a segfault and vim/gvim crashes.
I also use ctags and clang-completion
Comment by Alex Theiakos (alelos) - Wednesday, 11 April 2012, 10:34 GMT
It seems to be a problem with ctags. I removed the ctags package and C files work again.
packages:
gvim 7.3.495-1 / x86_64
ctags 5.8-3 / x86_64
Comment by Thomas Dziedzic (tomd123) - Friday, 13 April 2012, 00:05 GMT
I don't use ctags, but I encountered another crash myself and had to debug it.

I have attached the source for the package which enables debug symbols for vim.

It would be preferable if you used sudo extra-i686-build or extra-x86_64-build to create the debug package.

Hope this helps!
(application/x-gzip)    vim-7.3.495-1.src.tar.gz (5 KiB)
Comment by Thomas Dziedzic (tomd123) - Friday, 20 April 2012, 01:06 GMT
Please try vim-7.3.495-2 which I removed O2 from the CFLAGS because it seems to be the culprit with the python crashes.

Can you tell me if the latest vim has this crash or not?
Comment by Alex Theiakos (alelos) - Friday, 20 April 2012, 09:47 GMT
The last version (vim-7.3.495-2) works nice with ctags.

I dont get any more crashes with C/C++ files and ctags installed.

Thanks
Comment by Thomas Dziedzic (tomd123) - Friday, 20 April 2012, 13:14 GMT
Ok, it's definitely caused by turning on optimization for vim (O1 and O2).

I will keep this bug open until I find the actual problem.
Comment by arielp (ajp) - Friday, 20 April 2012, 14:57 GMT
It seems that patch 497 should fix this. ftp://ftp.vim.org/pub/vim/patches/7.3/7.3.497 (Well, not fixed per se, but avoided.)
Comment by Thomas Dziedzic (tomd123) - Friday, 20 April 2012, 15:27 GMT
p497 is a hack and is not a proper fix to this.
I'm guessing it was included so that people who compile vim with 4.7.0 and -O2 or -O1 will not experience a segfault but instead a buggy python interface.
Comment by arielp (ajp) - Friday, 20 April 2012, 15:43 GMT
Yeah, I was in a rush and didn't really read it. Sorry.
Comment by Thomas Dziedzic (tomd123) - Tuesday, 29 May 2012, 22:06 GMT
Fedora bug report: https://bugzilla.redhat.com/show_bug.cgi?id=817196

Loading...