On Thu, Aug 23, 2012 at 9:56 PM, Bram Moolenaar <[email protected]> wrote:
>
> Richard Brown wrote:
>
> > Hi, 7.3.449 fixed an issue where this autocommand and the following
> > sequence would cause a segfault:
> >
> > :autocmd BufWinLeave * if empty(&bt) | lclose | endif
> > :call setloclist(1, [{'bufnr': 1, 'lnum': 1, 'text': 'testing'}])
> > :lopen
> > ^wk
> > :q
> >
>
> Considering that 7.3.545 fixes a problem with autocommands, it's
> unlikely that it introduced the problem, but rather uncovered another
> problem.
>
> Does that sequence of commands segfault also for "vim -u NONE"?
>
Yes, I should have said that I was doing that, sorry. The backtrace didn't
seem to offer much before, but here it is for Included patches: 1-638, 638
Program received signal SIGSEGV, Segmentation fault.
0x00000001001553e5 in update_screen (type=40) at screen.c:478
478 if (wp->w_buffer->b_mod_set)
(gdb) bt
#0 0x00000001001553e5 in update_screen (type=40) at screen.c:478
#1 0x00000001001def0f in main_loop (cmdwin=0, noexmode=0) at main.c:1197
#2 0x00000001001debce in main (argc=3, argv=0x7fff5fbffbe8) at main.c:998
--
Richard Brown
--
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
