Vim + python users: anyone have problems with Vim patch 495?

wes · 2012-04-13 05:32:07

Hello. Since the recent upgrade to Vim 7.3.495, I cannot invoke python from
Vim. In 7.3.475, everything worked fine. Here is a minimal example. From
within vim,

:python print "hello"

Results in:

Vim: Caught deadly signal SEGV
Vim: Finished.
Segmentation fault

I reverted to 475, and all is well. Anyway, before I make a fuss, can anyone
else confirm this issue with the latest Vim +python setup? Just wanted to
make sure it wasn't something me-specific. Thanks.

FreeTheBee · 2012-04-13 07:05:11

I hadn't noticed yet, but it doesn't work on my system either . I just get a segmentation fault.

[edit]On my laptop it works without problems[/edit]

Last edited by FreeTheBee (2012-04-13 07:13:17)

Atragor · 2012-04-13 07:11:50

I can confirm - it segfaults on 'print', but python code that doesn't print anything seems to work, e.g.:

:python vim.current.buffer.append('test')

appends 'test' to current buffer.

upd: the same version compiled via ABS also didn't work.

Last edited by Atragor (2012-04-13 07:26:58)

wes · 2012-04-13 07:22:01

Cool. Thanks guys. I'll find the right place and submit a bug report then.

nineinchnick · 2012-04-13 12:44:00

Could you post a link to the bug report if/after you submit it? I would like to track progress on this.
I debug PHP with vim and xdebug and I hate to keep vim in IgnorePkg in pacman.conf.

EDIT: Found it on VIM mailing list.

Last edited by nineinchnick (2012-04-13 12:59:28)

Stebalien · 2012-04-13 15:53:27

nineinchnick wrote:

Could you post a link to the bug report if/after you submit it? I would like to track progress on this.
I debug PHP with vim and xdebug and I hate to keep vim in IgnorePkg in pacman.conf.
EDIT: Found it on VIM mailing list.

For others: https://groups.google.com/d/topic/vim_d … discussion

wes · 2012-04-13 19:28:07

Could you post a link to the bug report if/after you submit it?

Sorry you had to dig it up on your own- I meant to post it last night.

new · 2012-04-13 20:46:27

I am having the same issue on x86_64. Using the old 475 package works. However, recompiling 475 from source has the same issue as 495.

dohko · 2012-04-13 21:35:50

I compiled vim with python support yesterday and couldn't for the love of jebus understand why it was crashing when using python. This explains it all. I'm just a little bit curious, how do you archers install vim with python support?

guotsuan · 2012-04-13 22:21:31

I install vim with python support by " pacman -S gvim"

dohko wrote:

I compiled vim with python support yesterday and couldn't for the love of jebus understand why it was crashing when using python. This explains it all. I'm just a little bit curious, how do you archers install vim with python support?

tomd123 · 2012-04-19 19:36:43

I figured out a way to avoid the segfault, you will have to rebuild vim from abs and apply the following patch to the PKGBUILD:
https://gist.github.com/2423572

I'm guessing this has something to do with arch's and vim's buildflags somehow not playing well together.

Awebb · 2012-04-19 20:30:53

I can't invoke python at all, it says "Sorry, the command is not available in this version".

Uhm...?

Last edited by Awebb (2012-04-19 20:32:18)

tomd123 · 2012-04-19 21:15:22

You need to use gvim. vim doesn't have python (or any other interpreter support except perl).

edit: I meant the package gvim

Last edited by tomd123 (2012-04-19 21:15:57)

tomd123 · 2012-04-19 22:59:48

Even better, remove -O2 from CFLAGS and the crash doesn't happen. I'm guessing this has something to do with gcc 4.7.0 possibly

Edit: crashes with -O1 also..

Last edited by tomd123 (2012-04-19 23:16:18)

saline · 2012-04-20 04:30:55

tomd123 wrote:

I figured out a way to avoid the segfault, you will have to rebuild vim from abs and apply the following patch to the PKGBUILD:
https://gist.github.com/2423572
I'm guessing this has something to do with arch's and vim's buildflags somehow not playing well together.

This works with patch 496 and fixes python 3 support for me. Thanks a lot.

FreeTheBee · 2012-04-20 12:35:22

Today's upgrade to vim 7.3.495-2 fixed this issue for me.

Arch Linux

#1 2012-04-13 05:32:07

Vim + python users: anyone have problems with Vim patch 495?

#2 2012-04-13 07:05:11

Re: Vim + python users: anyone have problems with Vim patch 495?

#3 2012-04-13 07:11:50

Re: Vim + python users: anyone have problems with Vim patch 495?

#4 2012-04-13 07:22:01

Re: Vim + python users: anyone have problems with Vim patch 495?

#5 2012-04-13 12:44:00

Re: Vim + python users: anyone have problems with Vim patch 495?

#6 2012-04-13 15:53:27

Re: Vim + python users: anyone have problems with Vim patch 495?

#7 2012-04-13 19:28:07

Re: Vim + python users: anyone have problems with Vim patch 495?

#8 2012-04-13 20:46:27

Re: Vim + python users: anyone have problems with Vim patch 495?

#9 2012-04-13 21:35:50

Re: Vim + python users: anyone have problems with Vim patch 495?

#10 2012-04-13 22:21:31

Re: Vim + python users: anyone have problems with Vim patch 495?

#11 2012-04-19 19:36:43

Re: Vim + python users: anyone have problems with Vim patch 495?

#12 2012-04-19 20:30:53

Re: Vim + python users: anyone have problems with Vim patch 495?

#13 2012-04-19 21:15:22

Re: Vim + python users: anyone have problems with Vim patch 495?

#14 2012-04-19 22:59:48

Re: Vim + python users: anyone have problems with Vim patch 495?

#15 2012-04-20 04:30:55

Re: Vim + python users: anyone have problems with Vim patch 495?

#16 2012-04-20 12:35:22

Re: Vim + python users: anyone have problems with Vim patch 495?

Board footer