Benjamin Fritz wrote: > > > The attached test_vimrc.vim sets up a command that (on Windows) > > > generates a tags file asynchronously and then calls back into Vim using > > > --remote-expr to add that tags file to the 'tags' option. > > > > > > The test_vimrc.vim also sets the 'cscopetag' option to enable selecting > > > between multiple tag matches. > > > > > > After sourcing this test file, I can reliably make Vim crash as follows > > > (edit the "let ctags_exec" line to match your own exuberant ctags path): > > > > > > 1. cd to a project top-level directory with at least one large code > > > subdirectory following C/C++ coding practices of having function > > > declarations separate from function definitions. > > > 2. Execute the :Ctags command and wait for it to finish > > > 3. cd into the large code subdirectory and edit a code file > > > 4. Go to a function call within the code file > > > 5. Execute the :Ctags command again, but don't wait for it to finish > > > 6. Before the tags processing completes, use CTRL-] to select the tag > > > for the function your cursor is on (presumably, you will have 2 > > > matches, one for the function prototype and one for the function > > > definition) > > > 7. Wait for the :Ctags command to finish > > > 8. Try entering a number to select the tag to jump to > > > 9. Vim crashes > > > > > > I'm using gvim 7.4.629 64-bit on Windows 7. I do have a couple custom > > > patches applied but nothing affecting tags processing. > > > > Can someone reproduce it and get a stack trace, so that we know where it > > happens? Or a valgrind log, might be even better. > > > > Did you need a different kind of stack trace than the gdb "bt" backtrace I > provided?
Ah, that was a few days later. I don't spot anything in there that is a hint about what is wrong. Perhaps a valgrind log would help. Or someone who can look around with gdb about the variable values when it crashes. -- How To Keep A Healthy Level Of Insanity: 7. Finish all your sentences with "in accordance with the prophecy". /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\ /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ an exciting new programming language -- http://www.Zimbu.org /// \\\ help me help AIDS victims -- http://ICCF-Holland.org /// -- -- 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 --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
