On Wed, Apr 27, 2016 at 11:44:39AM +0100, Andrew Stewart wrote: > ...which seemed to work well, at least until Vim crashed: > > Vim: Caught deadly signal SEGV > Vim(85664,0x7fff7a952000) malloc: *** error for object 0x7ff2106739e8: > incorrect checksum for freed object - object was probably modified after > being freed. > *** set a breakpoint in > malloc_error_break to debug > > Vim: Finished. > Vim: Double signal, exiting > Abort trap: 6
That sounds like it might be related to the segfault I reported[0] recently. [0]: http://article.gmane.org/gmane.editors.vim.devel/58887 Cheers, -- James GPG Key: 4096R/331BA3DB 2011-12-05 James McCoy <james...@jamessan.com> -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
