On Sun, Jul 9, 2017 at 3:17 PM, Aron Griffis <agrif...@gmail.com> wrote:

> In fact, I just rebuilt from pristine 702 source to make sure:
>
> $ CFLAGS=-ggdb ./configure --enable-gui=no --without-x
> $ make
> $ cd src
> $ gdb ./vim
> (gdb) run
>
> (change the content of .vim/background and .vim/scheme, cause segfault)
>

I'm not sure why that last backtrace was so long. I just ran again and got
a shorter one:

(gdb) bt
#0  0x00007ffff6cbd64b in raise () from /lib64/libc.so.6
#1  0x00007ffff6cbf450 in abort () from /lib64/libc.so.6
#2  0x00007ffff6d03921 in __libc_message () from /lib64/libc.so.6
#3  0x00007ffff6d0e7a9 in _int_free () from /lib64/libc.so.6
#4  0x00007ffff6d1410e in free () from /lib64/libc.so.6
#5  0x00000000004dba25 in vim_free (x=0x9fce50) at misc2.c:1793
#6  0x000000000047a7b2 in discard_exception (excp=0x9fce50, was_finished=0)
at ex_eval.c:634
#7  0x000000000047a7d1 in discard_current_exception () at ex_eval.c:643
#8  0x000000000045f66a in check_due_timer () at ex_cmds2.c:1239
#9  0x000000000051c86e in WaitForChar (msec=2000,
interrupted=0x7fffffffd870) at os_unix.c:5500
#10 0x0000000000518718 in mch_inchar (buf=0x86d3fa <typebuf_init+58> "",
maxlen=68, wtime=-1, tb_change_cnt=5) at os_unix.c:481
#11 0x00000000005b0d6f in ui_inchar (buf=0x86d3fa <typebuf_init+58> "",
maxlen=68, wtime=-1, tb_change_cnt=5) at ui.c:195
#12 0x00000000004a6305 in inchar (buf=0x86d3fa <typebuf_init+58> "",
maxlen=206, wait_time=-1, tb_change_cnt=5) at getchar.c:3065
#13 0x00000000004a5fa2 in vgetorpeek (advance=1) at getchar.c:2841
#14 0x00000000004a437c in vgetc () at getchar.c:1608
#15 0x00000000004a4810 in safe_vgetc () at getchar.c:1804
#16 0x00000000004eac40 in normal_cmd (oap=0x7fffffffdc40, toplevel=1) at
normal.c:628
#17 0x00000000005e2391 in main_loop (cmdwin=0, noexmode=0) at main.c:1355
#18 0x00000000005e1c48 in vim_main2 () at main.c:908
#19 0x00000000005e143f in main (argc=1, argv=0x7fffffffde38) at main.c:419

-- 
-- 
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 vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Raspunde prin e-mail lui