Dominique Pelle wrote: > Vim-7.2.330 (huge, Linux x86-64, in GNOME terminal) > crashed while editing files. I can't reproduce it unfortunately. > > It happened when trying to modify a file. The file was in > Perforce, not checked-out, and trying to modify it caused > the Perforce-4.1 plugin to check-out the file. Vim crashed > at that time. File has been successfully checked-out. > > Maybe related to an issue which I reported a while > ago which also happened when checking out a file with > the Perforce plugin. But symptoms and stack trace were > very different. That issue was addressed by patch 7.2.189 > but it just was a workaround to something which should not > happen in the first place: > > Subject: [bug] infinite loop using 100% CPU in edit.c > To: vim_dev <[email protected]> > Date: Wed, 29 Apr 2009 19:04:18 +0200 > > http://groups.google.com/group/vim_dev/browse_thread/thread/efc4f27fe47c9= > be8# > > Hopefully the stack trace where it crashed (summarized > stack trace + full stack trace) is enough to track the issue:
I don't see a hint. Were you running valgrind? If yes then I wonder why the bad pointer wasn't detected earlier. -- hundred-and-one symptoms of being an internet addict: 92. It takes you two hours to check all 14 of your mailboxes. /// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\ /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ download, build and distribute -- http://www.A-A-P.org /// \\\ help me help AIDS victims -- http://ICCF-Holland.org ///
-- You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php
