Dominique Pellé wrote: > > I'll try with 32-bits Linux later too. > > I've tried with Linux 32 bits and there I could finally reproduce the > corruption > with vim-7.4.972 using the script below. Somehow, valgrind or asan do not > see any problem. I can also confirm that the bug is fixed when the latest > vim-7.4.976.
Most likely the pointer is into a data block which gets re-used for another block read from the file. Thus the pointer remains valid, the text that it points to changes. Valgrind doesn't see that problem. Only when the pointer would be very close to the end of the block, and after updating it there is no NUL after the pointer, it might go over the end of the block. But it's likely something prevents that from happening, there is always a NUL. -- Facepalm statement #5: "Petrol getting more expensive? Not for me, I'm always tanking for 20 dollars" /// Bram Moolenaar -- [email protected] -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
