On 2014-05-09, Dominique Pellé wrote: > Gary Johnson wrote: > > > I triggered a seg fault when I accidentally hit '&' instead > > of '^' in normal mode. I can easily reproduce it with the attached > > viminfo file (compressed for integrity) and by starting vim as > > > > vim -N -u NONE -i vimrc > > > > then typing > > > > & > > Hi Gary > > It looks like the bug already fixed by patch 7.4.245 > (you're using Vim-7.4.233). > > --- > changeset: 5802:80421d934ebd > tag: v7-4-245 > user: Bram Moolenaar <[email protected]> > date: Fri Apr 04 19:00:48 2014 +0200 > files: src/ex_cmds.c src/version.c > description: > updated for version 7.4.245 > Problem: Crash for "vim -u NONE -N -c '&&'". > Solution: Check for the pattern to be NULL. (Dominique Pelle) > ---
Thanks. I just pulled the latest and see that that pointer is now checked for NULL before calling strcmp(). Regards, Gary -- -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
