Ran Regev <[email protected]> wrote: > # alias eali > alias eali='vim ~/.alias' > # eali > Vim: Caught deadly signal SEGV > Vim: Finished. > Segmentation fault (core dumped) > > # gdb /usr/bin/vim core > <snip> > Reading symbols from /usr/bin/vim...(no debugging symbols found)...done. > [New LWP 3098] > > warning: Can't read pathname for load map: Input/output error. > [Thread debugging using libthread_db enabled] > Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1". > Core was generated by `vim /home/ran/.alias'. > Program terminated with signal 11, Segmentation fault. > #0 0xb77a5424 in __kernel_vsyscall () > (gdb) bt > #0 0xb77a5424 in __kernel_vsyscall () > #1 0xb72b2156 in kill () from /lib/i386-linux-gnu/libc.so.6 > #2 0x0813f890 in ?? () > #3 0x081411a5 in mch_exit () > #4 0x0810e418 in preserve_exit () > #5 <signal handler called> > #6 0x081ba4a5 in mf_get () > #7 0x080f5a58 in ?? () > #8 0x080fa20c in ml_open_file () > #9 0x080d4214 in readfile () > #10 0x0806f58e in open_buffer () > #11 0x0806660a in main () > (gdb) quit > > # vim > (inside vim - :e ~/.alias) > Vim: Caught deadly signal SEGV > Vim: Finished. > Segmentation fault (core dumped) > > > > Any idea? > > > Ran.
Hi I'm not seeing this bug using vim-7.4.648 on Linux x86_64. What version of Vim are you using? What is the content of ~/.alias file? Compile vim with -g -O0 to have more useful backtrace (I don't see line numbers in your stack trace). Try with: vim -u NONE ~/.alias Try also running vim with valgrind or asan (address sanitizer). 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/d/optout.
