On Tue, Jun 19, 2012 at 06:23:29PM -0700, Gary Johnson wrote: > I don't have all the details on this at the moment, but I ran out of > time to investigate further today. In summary, opening a new line > in a C comment causes Vim to dump core with various messages about > improper freeing of memory.
I can reproduce this on Solaris 11 with 7.3.555, but not 7.3.515. I specifically have to use libumem (an alternate malloc implementation that's got a bunch of debugging goodies in it), but the resulting core appears to have the same stack. FWIW, I only have to hit Enter once, and in fact, simply "o" will do the trick. Plus, the file need only contain "//" at the beginning of the first line -- no tabs, no comment content, no second comment line. The umem debugging utils say it's a write past end of buffer. Why that would be happening on a vim_free() call, I don't know. But umem confirms that the buffer involved is the same one allocated on line 1058 -- "leader". Danek -- 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
