François Ingelrest <[email protected]> wrote: > On 26 December 2013 14:01, Dominique Pellé wrote: >> If you can reproduce it, can you give a stack trace >> with gdb, and also try to reproduce it with valgrind >> or address sanitizer? > > I'm not sure how to get a meaningful stack trace: I compiled Vim with > -g and ran it with GDB, but all I get in the log file is: > > Starting program: /usr/local/bin/vim > > Program received signal SIGSEGV, Segmentation fault. > 0x00007ffff770e078 in main_arena () from /lib/x86_64-linux-gnu/libc.so.6 > A debugging session is active. > > Inferior 1 [process 27106] will be killed.
You need to: - build vim with -g -O0 - make sure vim is not stripped (uncomment #STRIP = /bin/true in vim/src/Makefile). Or run vim from the vim/src/. directory, as it is not stripped there. - start vim with gdb: $ cd vim/src $ gdb ./vim (gdb) run ... and when it crashes... (gdb) backtrace > As for Valgrind I never used it, any explanation on how to get it > running with Vim? $ cd vim/src $ valgrind --log-file=valgrind.log \ --track-origins=yes \ --num-callers=50 ./vim vim will be ~ 50 times slower when running with valgrind. Errors found will be logged in file valgrind.log. Regards 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]. For more options, visit https://groups.google.com/groups/opt_out.
