Currently Being ModeratedOct 1, 2011 6:24 AM (in response to jswetzen)
I seem to have fixed the issue when I opened ~/.viminfo and commented out everything.
Sledge hammer approach, I know, but it's progress, no? Got the idea from here:
If I run into undesirable side effects, I post more here. If anyone can site why this is a bad idea, I'd love to hear it before it burns me
Currently Being ModeratedOct 1, 2011 6:30 AM (in response to MrClow)
Nevermind, now I've got this:
vi(21203) malloc: *** error for object 0x7fe112504408: incorrect checksum for freed object - object was probably modified after being freed.
Here's hoping that might help someone more knowledgeable solve the problem...
Currently Being ModeratedOct 4, 2011 8:12 PM (in response to jswetzen)
Every time it crashes for me I get the following backtrace:
0 libsystem_kernel.dylib 0x00007fff9325382a __kill + 10
1 vi 0x000000010ac9ab71 0x10ab73000 + 1211249
2 libsystem_c.dylib 0x00007fff8cc46cfa _sigtramp + 26
3 libsystem_c.dylib 0x00007fff8cc46484 strncmp + 148
4 libcopyfile.dylib 0x00007fff930b8204 copyfile + 514
5 vi 0x000000010abd4887 0x10ab73000 + 399495
6 vi 0x000000010abac485 0x10ab73000 + 234629
7 vi 0x000000010abc17ab 0x10ab73000 + 321451
8 vi 0x000000010ac1e7cf 0x10ab73000 + 702415
9 vi 0x000000010ac27e09 0x10ab73000 + 740873
10 vi 0x000000010abec29e 0x10ab73000 + 496286
11 vi 0x000000010abee9d2 0x10ab73000 + 506322
12 vi 0x000000010ab73d04 0x10ab73000 + 3332
I recently had to switch back to Lion after downgrading and was disapointed to see this problem still occuring on a new laptop shipped with Lion. Has anyone looked through the vim source code for calls to copyfile()? Did Apple change something with this API in Lion?
Currently Being ModeratedOct 10, 2011 7:34 PM (in response to dlarimer)
No crashes in the past 4 days, when I normally crashed a couple of times per hour while writing code. At this point, I am convinced that building vim from source (not mac ports) with debug enabled is a working solution.
Currently Being ModeratedApr 21, 2012 8:18 AM (in response to dlarimer)
@dlarimer – Thanks for the tip. I've installed from source, but I'm not sure where I was supposed to use the `-g` flag.
For any future visitors to this little post who are as new at compiling from source as me, here are all the steps:
Download vim and unzip it. Then cd into the directory with it and
sudo make install
sudo make install clean
This will install the vim executables in /usr/loca/bin. If you want them to be in /usr/bin (where they used to be), you'll have to move them.
I just did this, so I don't know how well it's working yet, but you give me hope, @dlarimer. :-)
Currently Being ModeratedMay 18, 2012 8:33 PM (in response to jswetzen)
I found that vim will crash if you're editing files with extended attribute.
You may found @ symbol if you do a ls -l
Once I remove the extended attributes, my vim doesn't crash already. It seems like the vim shipped with lion doesn't support extended attributes.
Hope this help.
Currently Being ModeratedOct 3, 2012 9:47 AM (in response to jswetzen)
+1, problem confirmed here, both with 7.3 and vim installed from brew via https://raw.github.com/AndrewVos/homebrew-alt/master/duplicates/vim.rb
I rebuilt from source (http://www.vim.org/mercurial.php) and so far so good ...