On Wednesday 02 February 2011 15:35:33 Christian Brabandt wrote:
> Hi Bram!
> On Di, 01 Feb 2011, Bram Moolenaar wrote:
> > Looking through the code I found one situation where it
> > would read
> >
> > uninitialized memory:
> > :set stl=%!'asdf%'
> >
> > However, the valgrind log looks different from what you
> > show. I suspect there is another problem. Or the same
> > problem in another situation. Can you check with patch
> > 7.3.112 if you can still reproduce the valgrind warning?
> Yes, and I can still reproduce the crash with this crash.vim
> file:
> #v+
> $ mkdir -p /tmp/vim-crash
> $ cd /tmp/vim-crash
> $ touch {1..65}
> $ cat crash.vim
> function! MyTabLine()
> let s = ''
> for i in range(tabpagenr('$'))
> let s .= '%#TabLine#'
> let s .= ' %{MyTabLabel(' . (i + 1) . ')} '
> endfor
> return s
> endfunction
> function! MyTabLabel(n)
> return a:n
> endfunction
> set tabline=%!MyTabLine()
> $ vim -u crash.vim --noplugin
> $ vim -u crash.vim --noplugin -N -i NONE --cmd ':set tpm=65'
> -p /tmp/vim-crash/*
> Vim: Caught deadly signal SEGV
> Vim: Finished.
> zsh: segmentation fault (core dumped) ./vim -u crash.vim
> --noplugin -N -i NONE --cmd ':set tpm=65' -p
> $
> #v-
feeling adventurous, i tried this exact thing on my (suse
linux 11.2) box and no bomb for me, just 66 tab pages with
numbers for labels
my vim is Big, 7.3.112, with GTK2 gui
sc
--
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
