On 25-May-2010 reckoner <[email protected]> wrote: > Lech: > > Thanks for your reply. I'm attaching the _vimrc (sorry it's kind of messy). > > The tricky part is that I can't reliably reproduce the error, even > though it happens consistently. In other words, I can't exactly > articulate a finite series of steps that lead to the crash other than > I keep doing <C-N> and <C-P> until it does happen. It seems like it > depends on the accumulation of a number of previous events before it > finally happens. Also, it doesn't seem to matter which python files > are being used. I have run into this problem before while editing > many different python files. > > The only thing is that I recompiled the gvim binary using a new > python installation (Python version 2.6) using the PYTHON and > PYTHON_VER flags > with DYNAMIC_PYTHON=no and using Visual Studio 2008. I then took the > existing vim installation (which is vim 7.2 from the installer) and > then simply replaced the gvim binary with the one I personally > compiled for Python version 2.6. > > Thanks again. Any help appreciated.
I can reproduce an invalid memory access for <C-X><C-T> and <C-X><C-K>, but have no clue how to cause this for <C-N> or <C-P>. Are you sure this happens when you do <C-N> or <C-P>? If so, please, do your best to find the right steps to make the problem appear. -- Cheers, Lech -- 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
