Matt Wozniski wrote: >> I tried to reproduce it but I could not. > > Yeah, I'm not surprised... the fact that it seems tied to a hash > table resizing makes me think that it's very much tied to the number > of plugins I have loaded, the number of variables I have defined, and > a whole bunch of other, less obvious factors.... > >> Which command(s) >> do you use to "step to line 300"? > > at the :debug prompt, just pressing s<CR> and then <CR> repeatedly > until I hit 300.
I still have not been able to reproduce it. But as you said, there might be something subtle to trigger the memory reallocation. It'd be nice to have a an automated way to reproduce it. Does the following command for example reproduce the error? (it does not for me). $ yes | tr y s | valgrind vim -D -c ':Explore' 2> valgrind.log If you don't mind, maybe sharing your ~/.vimrc and a tar or your ~/.vim/ directory could help others to reproduce it. Cheers -- Dominique --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
