Hi Dominique,
Which operating system and CPU are you using?
I'm running a 64 bit install of Ubuntu 9.10. The output of the command `uname -a' is: Linux laptop 2.6.31-22-generic #61-Ubuntu SMP Wed Jul 28 02:02:56 UTC 2010 x86_64 GNU/Linux
You can try to reproduce the bug with valgrind (if it's supported by your OS...).
Thanks for your suggestion. I just found out that the following line in my ~/.vimrc is the apparent cause of the crash:
:set history=5000 viminfo='250,<0,r/tmp
Unfortunately the crash disappeared right around the time I realized
this, just before I received your message, which means I didn't get a
chance to run Vim under Valgrind. The crash hasn't reappeared since, so
I'm guessing the crash was related to the contents of my ~/.viminfo file
which has since been changed by Vim. Because I didn't realize ~/.viminfo
was involved until the crash disappeared I don't have a copy of the
faulty ~/.viminfo contents... :-(
I think the crash might be related to the highlighting of the last used search pattern (from a previous Vim instance) because the backtrace I posted earlier in this thread starts with regmatch(), regtry(), vim_regexec_both(), etc. and the crash seemed to be related to the contents of my ~/.viminfo file.
On the off chance that it's useful to some hardcore/psychic Vim hacker I've attached my ~/.viminfo file to this message. I had to slightly anonymize the file because of course it contains lots of info about my private documents, I hope this doesn't make it useless; at least the history of last used search patterns is intact, but don't ask me how half those entries got there because I wouldn't know how to type those non-ASCII characters anyway (I guess these entries are caused by Vim plug-ins?!).
- Peter Odding -- 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
viminfo-anonymized
Description: Binary data
