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. On 5/25/2010 1:06 PM, Lech Lorens wrote:
On 25-May-2010 reckoner<[email protected]> wrote:Hi, When I try to complete using C-N or C-P in insert mode, I routinely get a crash. I just download the latest svn svn co https://vim.svn.sourceforge.net/svnroot/vim/vim7 I have the following in my _vimrc: set complete+=s*.py set complete-=k complete+=k Below is the error listing: Unhandled exception at 0x00547c75 in gvim.exe: 0xC0000005: Access violation reading location 0x0286c000. First-chance exception at 0x00547c75 in gvim.exe: 0xC0000005: Access violation reading location 0x0286c004. Unhandled exception at 0x00547c75 in gvim.exe: 0xC0000005: Access violation reading location 0x0286c004. First-chance exception at 0x00547e25 in gvim.exe: 0xC0000005: Access violation reading location 0x0286c000. Unhandled exception at 0x00547e25 in gvim.exe: 0xC0000005: Access violation reading location 0x0286c000. First-chance exception at 0x00547e37 in gvim.exe: 0xC0000005: Access violation writing location 0x0286c000. Unhandled exception at 0x00547e37 in gvim.exe: 0xC0000005: Access violation writing location 0x0286c000. First-chance exception at 0x00547e37 in gvim.exe: 0xC0000005: Access violation writing location 0x0286c000. The thread 'Win32 Thread' (0x1054) has exited with code 0 (0x0). Unhandled exception at 0x00547e37 in gvim.exe: 0xC0000005: Access violation writing location 0x0286c000. and here is the call stack from VisualStudio 2008:gvim.exe!ins_compl_add_infercase(unsigned char * str=0x0283a8d3,int len=1, int icase=1, unsigned char * fname=0x0285c118, int dir=1, int flags=0) Line 2280 + 0x18 bytes C gvim.exe!ins_compl_files(int count=40, unsigned char * * files=0x0285c1d0, int thesaurus=1, int flags=1, regmatch_T * regmatch=0x0012f740, unsigned char * buf=0x0283a898, int * dir=0x0012f730) Line 3062 + 0x29 bytes C gvim.exe!ins_compl_dictionaries(unsigned char * dict_start=0x0222d1fa, unsigned char * pat=0x028403e0, int flags=1, int thesaurus=1) Line 2964 + 0x21 bytes C gvim.exe!ins_compl_get_exp(pos_T * ini=0x007d6c0c) Line 4042 + 0xd2 bytes C gvim.exe!ins_compl_next(int allow_get_expansion=1, int count=1, int insert_match=1) Line 4439 + 0xa bytes C gvim.exe!ins_complete(int c=14) Line 5072 + 0x21 bytes C gvim.exe!edit(int cmdchar=105, int startln=0, long count=1) Line 1348 + 0x9 bytes C gvim.exe!invoke_edit(cmdarg_S * cap=0x0012fb80, int repl=0, int cmd=105, int startln=0) Line 8911 + 0x14 bytes C gvim.exe!nv_edit(cmdarg_S * cap=0x0012fb80) Line 8884 + 0x14 bytes C gvim.exe!normal_cmd(oparg_S * oap=0x0012fc1c, int toplevel=1) Line 1188 + 0x12 bytes C gvim.exe!main_loop(int cmdwin=0, int noexmode=0) Line 1211 + 0xb bytes C gvim.exe!VimMain() Line 955 + 0x9 bytes C gvim.exe!WinMain(HINSTANCE__ * hInstance=0x00400000, HINSTANCE__ * hPrevInst=0x00000000, char * lpszCmdLine=0x00222466, int nCmdShow=10) Line 125 + 0xe bytes C gvim.exe!__tmainCRTStartup() Line 263 + 0x2c bytes C gvim.exe!WinMainCRTStartup() Line 182 C any help appreciated.I'll be happy to help but I can't reproduce the problem. Would it be possible for you to share your _vimrc, the file you edit while getting the crash and the *.py files you use as your thesaurus files? If not, can you simplify the procedure for getting the crash in such a way that you can share the details? Thanks!
-- 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
_vimrc
Description: Binary data
