суббота, 8 сентября 2012 г., 0:00:19 UTC+4 пользователь Bram Moolenaar написал:
> > That actually did not fix the problem: gcc optimized build now behaves
> > like non-optimized one, thats all. I still get a crash where I was
> > getting it before (aurum, "AuDiff rev1 1 rev2 tip **"). And I still
> > observe invalid number of lines (1041 lines with last one truncated).
>
> > I don't get invalid number of lines if I replace "expand("<amatch>")"
> > with "bufname(+expand("<abuf>"))". Doing the same in aurum does not
> > fix the crash. Crash happens at the very end of "fileinfo" function 
> > from buffer.c. The following patch seems to fix the crash:
>
> And: 
> 
> > Previous patch missed one length decrement and thus was invalid. There
> > was also no need to introduce one new variable, here is the updated
> > one. There is still one issue: at the end of :file outputs garbage is
> > shown meaning that something is wrong. I currently do not know how to
> > fix this or reproduce without using aurum.
> 
> So what is the simplest way to reproduce this crash?

After the patch there is no crash anymore, just seeing garbage. Before it was 
crashing when I did

    vim -c 'AuDidd rev1 1 rev2 tip **'
while current directory is inside aurum repository. The simplest way I know is 
to do

    mkdir test && cd test
    hg clone https://bitbucket.org/ZyX_I/frawor
    hg clone https://bitbucket.org/ZyX_I/aurum
    vim -u /dev/null -N --cmd 'let &rtp=getcwd()."/frawor,".getcwd()."/aurum"' \
        -c 'cd aurum' \
        -c 'AuDiff rev1 1 rev2 tip **'
I have no idea why initial "longfilenamebug.vim" file is not crashing: STRCPY 
that I replaced with STRNCPY must overwrite something in both cases (and in 
that file filename is much longer). Now if you do ":file" after this you will 
see garbage at the end.

I found another issue though: "python anything_that_throws_exception" is a 
crash. I don't think it is related, will explore this now.

-- 
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

Raspunde prin e-mail lui