Christian Brabandt wrote: > But ./vim 2>asan.log at least shows this: > vim9execute.c:1367:14: runtime error: member access within null pointer of > type 'struct isn_T'
That's an error reported by ubsan (undefined behavior sanitizer (not asan, address sanitizer). You either built with ubsan only (which by default does not abort on errors) or you built with ubsan & asan at the same time. ubsan errors are generally less severe than asan errors. Netheless, they are still bugs which should be fixed. > > Try putting also full path such as log_path=/tmp/asan.log > > otherwise if vim changes the current directory, it may be hard > > to know where asan.log is. Or run ./vim 2> log asan.log. > > > > Consider also trying with valgrind. > > Ah yes, forgot about it. Attached. > > (I should probably compile without python). Yes, Python causes annoying false errors with valgrind, unless you build your own python library using "configure --without-pymalloc". The easiest workaround to silence them is to build vim without python if that's possible in your case. Dominique -- -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/CAON-T_gpgCy_U9KE1QgLhMOgrCTXb951X2_JAJbQR7vNpqXNxg%40mail.gmail.com.
