Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 309851 - app-editors/vim 7.2.376 crashes immediately with 'abort trap' on invocation
Summary: app-editors/vim 7.2.376 crashes immediately with 'abort trap' on invocation
Status: RESOLVED FIXED
Alias: None
Product: Gentoo/Alt
Classification: Unclassified
Component: Prefix Support (show other bugs)
Hardware: x86 OS X
: Highest major (vote)
Assignee: Gentoo Prefix
URL: http://bugs.gentoo.org/show_bug.cgi?i...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-16 20:40 UTC by Robin Randhawa
Modified: 2010-03-16 21:53 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
Output of pertinent tools to assist with debugging (vim-abort.info,23.53 KB, text/plain)
2010-03-16 20:41 UTC, Robin Randhawa
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Robin Randhawa 2010-03-16 20:40:02 UTC
A gentoo update in the last few days seems to have nixed vim. I see that Bug #293631 (referenced in the URL) seems to have had similar problems in the past so I'll try and use that bug report as a template in the hope that I convey enough pertinent information.

Some points to bear in mind:

1. Attempting to rebuild didn't help.
2. Attempting to rebuild with USE="-python" didn't help.
3. The update I allude to above did rebuild the compiler

The attachment that follows contains various logs etc.

Thanks.
Comment 1 Robin Randhawa 2010-03-16 20:41:06 UTC
Created attachment 223957 [details]
Output of pertinent tools to assist with debugging
Comment 2 Robin Randhawa 2010-03-16 21:32:15 UTC
Another bit of information : If I delete $HOME/.vimrc, then vim is able to launch without aborting. This doesn't seem to have anything to do with the content of the file - I get the abort even with an empty .vimrc.

Comment 3 Jeremy Olexa (darkside) (RETIRED) archtester gentoo-dev Security 2010-03-16 21:53:51 UTC
vim_src_prepare() was not being called again. I fixed this before and fixed it for this version too.