With the latest build I get SIGABORT when exiting MacVim

[GoogleCodeExporter]

Where is the trace from gdb:

Vim(3438,0x7fff73570180) malloc: *** error for object 0x7274732f3c736a2d: 
pointer being freed was not allocated

*** set a breakpoint in malloc_error_break to debug

Program received signal SIGABRT, Aborted.
0x00007fff83446212 in __pthread_kill ()
(gdb) where
#0  0x00007fff83446212 in __pthread_kill ()
#1  0x00007fff8b594b54 in pthread_kill ()
#2  0x00007fff8b5d8dce in abort ()
#3  0x00007fff8b5ac9b9 in free ()
#4  0x00000001001747b8 in odb_end ()
#5  0x0000000100196bb5 in getout ()
#6  0x0000000100056da7 in ex_quit ()
#7  0x0000000100061853 in do_cmdline ()
#8  0x00000001000c9a65 in nv_colon ()
#9  0x00000001000d4eb0 in normal_cmd ()
#10 0x00000001

Hope it helps.

Original issue reported on code.google.com by ksibi...@gmail.com on 19 May 2013 at 10:11

[GoogleCodeExporter]

Thanks for the report.

What steps do you take to reproduce this?

Does the same thing happen if you start with "mvim -f -u NONE -U NONE"?

Original comment by bjorn.winckler@gmail.com on 20 May 2013 at 8:08

[GoogleCodeExporter]

Here is more info. I am running macvim in the terminal mode. I don't see the 
problem if I don't load my plugins. So it must be triggered by using some of 
the vimscript. Also I just checked that it doesn't happen when I use official 
vim repository and compiling with huge setting and no gui enabled. 

It could be related to new changes to ruby and python bindings, even though I 
don't think any of my plugins use them. 

Not sure if it helps. 

Original comment by ksibi...@gmail.com on 20 May 2013 at 4:06

[GoogleCodeExporter]

The problem is in the ODB editor related code which is specific to MacVim (see 
the "odb_end()" function call in the backtrace?), so that explains why it 
doesn't happen in the official vim code.

Do you think you can eliminate which plugin is causing the problem (by removing 
them and adding them back aone at a time)?  Otherwise, maybe tell me which 
plugins you use and I'll see if I can reproduce.

Do you use the ODB editor functionality?  (This is a remote editing protocol 
implemented by some programs such as Cyberduck, Xcode (at least pre 4.0) and 
others.)

Original comment by bjorn.winckler@gmail.com on 20 May 2013 at 6:06

[GoogleCodeExporter]

I just did another test once again, and it crashes even without a single plugin 
enabled. So now i'm positive that it is not plugin related.

Here is how I configure it:

./configure --enable-pythoninterp --enable-rubyinterp --enable-cscope 
--enable-multibyte --with-features=huge --enable-gui=macvim

Btw, i'm not using remote editing functionality. Simply compiling it and 
running it from macvim directory:

./src/MacVim/build/Release/MacVim.app/Contents/MacOS/Vim -u NONE -U NONE

results in crash for me.

Original comment by ksibi...@gmail.com on 20 May 2013 at 7:21

[GoogleCodeExporter]

I had a look and bad code is generated under certain circumstances.  Which 
exactly I have not managed to figure out, but you should try compiling with

CC=clang ./configure ...

and see if that fixes the problem.

Original comment by bjorn.winckler@gmail.com on 8 Jun 2013 at 4:51

[GoogleCodeExporter]

Yep, that was it. I don't see that issue if I compile with clang. Thanks.

Original comment by ksibi...@gmail.com on 9 Jun 2013 at 8:54

[GoogleCodeExporter]

Original comment by bjorn.winckler@gmail.com on 10 Jun 2013 at 5:58

• Changed state: WontFix