Elimar Riesebieter <[email protected]> wrote: > Hi all, > > I tried to build v7.4.1444 and got: > > (1 of 1): Line2^M"test_cdo.res" [New File]^[[64;16H^[[K^[[64;16H[New] 0L, 0C > written^M^M¬ > Executed 2 tests^M"messages"^[[64;12H^[[K^[[64;12H23L, > 521C^[[64;12H^[[K^[[64;12H28L, 600C written^M^M¬ > ^[[?1l^[>^[[34h^[[?25h^[[?1049lVIMRUNTIME=../../runtime; export VIMRUNTIME; > ../vim -f -u unix.vim -U NONE --noplugin --not-a-term -u NONE -U NONE -S > runtest.vim test_channel.vim¬ > ^[[?1049h^[[?1h^[=^[[1;64r^[[34l^[[34h^[[?25h^[[27m^[[24m^[[23m^[[0m^[[H^[[J^[[?25l^[[64;1H"test_channel.vim" > 573 lines, 15676 characters^M^M¬ > Executing Test_call()^[[34h^[[?25h^M^M¬ > ^[[?25lExecuting Test_channel_handler()^[[34h^[[?25h^M^[[?1l^[>^[[?1049lVim: > Caught deadly signal SEGV^M¬ > ^M¬ > Vim: Finished.^M¬ > ^[[64;1HSegmentation fault (core dumped)¬ > Makefile:130: recipe for target 'test_channel.res' failed¬
Can you give us a backtrace with gdb? You can get it from the core file using: $ cd vim/src/testdir $ make clean $ rm core $ make test_channel.res (I assume this will crash and create a core file for you) $ gdb ../vim core (gdb) backtrace I tried running that test with valgrind and vim-7.4.1444. Valgrind did not detect invalid memory access. It found a leak (with vim compiled with -DEXITFREE) but that would not explain the crash. Not sure how to fix that leak: ==10305== 16 bytes in 1 blocks are definitely lost in loss record 76 of 363 ==10305== at 0x4C2AB80: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==10305== by 0x4CC3DB: lalloc (misc2.c:920) ==10305== by 0x4CF5B4: alloc_clear (misc2.c:842) ==10305== by 0x5AD141: channel_parse_json (channel.c:1109) ==10305== by 0x5AEA9E: channel_read_json_block (channel.c:1987) ==10305== by 0x43B617: common_channel_read (eval.c:10468) ==10305== by 0x445AC1: call_func (eval.c:8913) ==10305== by 0x449112: get_func_tv (eval.c:8712) ==10305== by 0x447A4F: eval7 (eval.c:5239) ==10305== by 0x447C73: eval6 (eval.c:4890) ==10305== by 0x447EF3: eval5 (eval.c:4706) ==10305== by 0x448B84: eval4 (eval.c:4401) ==10305== by 0x448B84: eval3 (eval.c:4316) ==10305== by 0x448D14: eval2 (eval.c:4248) ==10305== by 0x448D14: eval1 (eval.c:4176) ==10305== by 0x44914D: eval0 (eval.c:4136) ==10305== by 0x44FFF0: ex_let (eval.c:1951) ==10305== by 0x46FAC7: do_one_cmd (ex_docmd.c:2921) ==10305== by 0x46FAC7: do_cmdline (ex_docmd.c:1107) ==10305== by 0x444EFD: call_user_func (eval.c:25268) ==10305== by 0x4459FE: call_func (eval.c:8883) ==10305== by 0x451094: func_call (eval.c:9872) ==10305== by 0x445AC1: call_func (eval.c:8913) ==10305== by 0x449112: get_func_tv (eval.c:8712) ==10305== by 0x44E34B: ex_call (eval.c:3527) ==10305== by 0x46FAC7: do_one_cmd (ex_docmd.c:2921) ==10305== by 0x46FAC7: do_cmdline (ex_docmd.c:1107) ==10305== by 0x444EFD: call_user_func (eval.c:25268) ==10305== by 0x4459FE: call_func (eval.c:8883) ==10305== by 0x449112: get_func_tv (eval.c:8712) ==10305== by 0x44E34B: ex_call (eval.c:3527) ==10305== by 0x46FAC7: do_one_cmd (ex_docmd.c:2921) ==10305== by 0x46FAC7: do_cmdline (ex_docmd.c:1107) ==10305== by 0x444EFD: call_user_func (eval.c:25268) ==10305== by 0x4459FE: call_func (eval.c:8883) ==10305== by 0x449112: get_func_tv (eval.c:8712) ==10305== by 0x44E34B: ex_call (eval.c:3527) ==10305== by 0x46FAC7: do_one_cmd (ex_docmd.c:2921) ==10305== by 0x46FAC7: do_cmdline (ex_docmd.c:1107) ==10305== by 0x44DF16: ex_execute (eval.c:23486) ==10305== by 0x46FAC7: do_one_cmd (ex_docmd.c:2921) ==10305== by 0x46FAC7: do_cmdline (ex_docmd.c:1107) ==10305== by 0x463FF1: do_source (ex_cmds2.c:3591) ==10305== by 0x46484B: cmd_source (ex_cmds2.c:3204) ==10305== by 0x46FAC7: do_one_cmd (ex_docmd.c:2921) ==10305== by 0x46FAC7: do_cmdline (ex_docmd.c:1107) ==10305== by 0x40DEE1: exe_commands (main.c:2918) ==10305== by 0x40DEE1: main (main.c:955) 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/d/optout.
