Neil Bird wrote: > Around about 07/04/06 13:56, Bram Moolenaar typed ... > >>> The check for the current buffer to be locked was a bit too generic. > >>> I'll explicitly allow using ":edit" without an argument. > >> What about :checktime ? Says it's postponed till after the autocmd, so > >> should it be OK too? > > Hmm, it seems so. I'll add an exception for that too. > > Well, I no longer get the two errors about not being able to edit, but I'm > back to crashes :-( [vim 7.0e] > > The original problem (crashing when checking out a file during diff mode > 'dp') seems to have actually been fixed, or, at least, it now hasn't crashed > for me. > > However, the newer instance (a checkout triggered by 'z=' spell checking) > has gotten worse. I get an error (sometmies SEGV, sometimes ABRT) and then > vim hangs: > > *** glibc detected *** free(): invalid next size (fast): 0x09926868 *** > Vim: Caught deadly signal ABRT > Vim: preserving files...
Apparently your FileChangedRO autocommand does something nasty. I suspect we need to detect that nastyness and disallow it. Any idea what the nasty bit could be? After some pointers go wrong anything can happen, thus how it crashes exactly is not interesting. It could help to use a library that forbids access to freed memory, like efence. Then the error is detected much earlier and a stack trace may provide more useful info. -- "Hit any key to continue" does _not_ mean you can hit the on/off button! /// 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://www.ICCF.nl ///
