Dominique Pellé wrote: > >> This patch causes a segfault at eval.c::17177 due to a trivial reason. > >> > >> The attached patch fixes it. > > > > Thanks! Unfortunately valgrind does not find this kind of error. > > The address sanitizer (asan) would find such bugs. It finds stack > and global variable corruptions not detected by valgrind. And it's > much faster than valgrind. On the other hand, asan does not find > uninitialized memory access found by valgrind. > > Attached is a patch to offer the option to build vim with asan.
Thanks. I assume this works with gcc, or does it also work with clang? When an error is found, how is it reported? -- Would you care for a drink? I mean, if it were, like, disabled and you had to look after it? /// 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.
