search

rzyns / macvim

Automatically exported from code.google.com/p/macvim
0 stars 0 forks source link

MacVim + Syntastic yields Caught deadly signal BUS #426

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?

Install and activate Syntastic, e.g. by adding, e.g. to your .vimrc:

let g:syntastic_auto_loc_list=1
let g:syntastic_enable_signs=1

Make sure you have a Syntastic-compatible syntax checker in your path, e.g. for 
Python install flake8

Use MacVim launched from command line to edit and then save file with syntax 
error. Syntastic frame will pop up highlighting syntax errors. Ingore syntax 
errors and attempt to save and quit.

What is the expected output? What do you see instead?

Expect successful save and quit. Get "Vim: Caught deadly signal BUS" and 
runaway CPU usage.

Using Macvim snapshot 64.  OS X 10.7.4.

Note you do not get the deadly signal BUS if you fix the syntax errors.

Original issue reported on code.google.com by mjwilli...@gmail.com on 6 Sep 2012 at 6:21

GoogleCodeExporter commented 9 years ago 
Try downloading the latest snapshot (65 at this point in time). If that fails, 
please send me the crash log (look under ~/Library/Logs).

Original comment by bjorn.winckler@gmail.com on 12 Sep 2012 at 8:05

GoogleCodeExporter commented 9 years ago 
Sorry, I'm running OS X 10.7. Snapshot 65 is apparently 10.8+ only.

There is no vim/MacVim log in ~/Library/Logs. I should have added that, because 
of the runaway CPU usage I have to "kill -9" the Vim process, which may prevent 
it from writing a crash log.

Original comment by mjwilli...@gmail.com on 13 Sep 2012 at 10:05

GoogleCodeExporter commented 9 years ago 
There are builds of snapshot 65 for 10.7 available:

https://github.com/b4winckler/macvim/wiki/ChangeLog

Original comment by bjorn.winckler@gmail.com on 13 Sep 2012 at 10:22

GoogleCodeExporter commented 9 years ago 
With 65, on save and quit of a file with a syntax error, I get in the status 
line "E855: Autocommands caused command to abort".

Original comment by mjwilli...@gmail.com on 13 Sep 2012 at 10:26

GoogleCodeExporter commented 9 years ago 
Sounds like you have a config/plugin problem. The troubleshooting guide may be 
of help when trying to track down this issue:

https://github.com/b4winckler/macvim/wiki/ChangeLog

You can also try asking for help at the vim_use Google Group. At any rate, this 
is no longer an issue with MacVim.

Original comment by bjorn.winckler@gmail.com on 13 Sep 2012 at 10:28