Loading ...
Sorry, an error occurred while loading the content.

Re: Vim 7.4a ready for beta testing (test96 FAILED)

Expand Messages
  • Bram Moolenaar
    ... If you can t reproduce a problem you had earlier, it s likely that something else matters. Can you run the test under valgrind? There is a line in
    Message 1 of 36 , Jul 10, 2013
    • 0 Attachment
      Raf wrote:

      > > > Bram Moolenaar wrote:
      > > >
      > > > > Announcing: Vim (Vi IMproved) version 7.4a BETA
      > > > >
      > > > > This is the first BETA release of Vim 7.4.
      > > > >
      > > > > Please check that the distribution is OK. I haven't done one for a long
      > > > > time. Report anything that isn't right. That includes a crash but also
      > > > > a typo in the documentation or a missing file.
      > > >
      > > > mid-2010 macbookpro
      > > > macosx-10.6.8
      > > > gcc-4.2.1
      > > >
      > > > obtained vim-7.4a.002 via hg (same result via ftp).
      > > >
      > > > configure \
      > > > --disable-darwin \
      > > > --with-x \
      > > > --enable-gui=motif \
      > > > --enable-multibyte \
      > > > --with-mac-arch=current \
      > > > --with-features=huge \
      > > > --disable-acl
      > > >
      > > > Test results:
      > > > test96 FAILED
      > > > TEST FAILURE
      > > >
      > > > diff -u test96.ok test96.failed
      > > > --- test96.ok 2013-07-08 10:12:36.000000000 +1000
      > > > +++ test96.failed 2013-07-08 10:15:31.000000000 +1000
      > > > @@ -4,6 +4,8 @@
      > > > - quickfix claims that the file name displayed is: test://bar.txt
      > > > Test B:
      > > > - number of window open: 2
      > > > +Test B:
      > > > + - number of window open: 2
      > > > Test C:
      > > > - 'buftype' of the location list window: quickfix
      > > > - buffer displayed in the 2nd window: test://quux.txt
      > > >
      > > > i.e. the "Test B" section of the file is repeated.
      > >
      > > That's strange. Please check that your version of src/testdir/test96.in
      > > is the same as
      > > https://code.google.com/p/vim/source/browse/src/testdir/test96.in
      >
      > it's the same.
      >
      > MD5 (/usr/local/src/vim74/src/testdir/test96.in) = 3222973df5598f7ff3297d3cf9b5ecd9
      >
      > i've tried with three separate copies of 7.4a.010:
      >
      > hg (https://vim.googlecode.com/hg/) test96 fails
      > hg (https://code.google.com/p/vim) test96 fails
      > ftp (ftp.vim.org) test96 passes
      >
      > how wierd is that?
      >
      > the two hg versions are the same but there are some differences
      > between them and the ftp version. the differences are that the
      > ftp version has older versions of:
      >
      > Makefile
      > runtime/compiler/checkstyle.vim
      > runtime/compiler/javac.vim
      > runtime/compiler/php.vim
      > runtime/compiler/se.vim
      > runtime/compiler/tcl.vim
      > runtime/compiler/tidy.vim
      > runtime/compiler/xmllint.vim
      > runtime/doc/diff.txt
      > runtime/doc/options.txt
      > runtime/doc/todo.txt
      > runtime/doc/uganda.txt
      > runtime/doc/version7.txt
      > runtime/plugin/tohtml.vim
      > runtime/synmenu.vim
      > runtime/syntax/2html.vim
      > runtime/syntax/help.vim
      > src/po/nl.po
      > src/po/pl.UTF-8.po
      > src/po/pl.cp1250.po
      > src/po/pl.po
      > src/po/ru.cp1251.po
      > src/po/ru.po
      >
      > i don't know if that helps. the actual diff can be found at
      > http://raf.org/tmp/vim74a.010-ftp-v-code.google.com-p-vim.diff
      > if it's of any use.
      >
      > it's odd that yesterday the ftp version of 7.4a.002 failed but
      > today the ftp version of 7.4a.010 passed. i just tested the ftp
      > version again at every patchlevel up to 010 and they all worked.
      > the hg version still fails though. bizarre.

      If you can't reproduce a problem you had earlier, it's likely that
      something else matters. Can you run the test under valgrind? There is
      a line in src/testdir/Makefile you can uncomment.

      The test is about location lists, the runtime files should not matter.
      If they do, it might be that things shift around in memory and trigger
      the problem somehow.

      --
      God made machine language; all the rest is the work of man.

      /// Bram Moolenaar -- Bram@... -- http://www.Moolenaar.net \\\
      /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
      \\\ an exciting new programming language -- http://www.Zimbu.org ///
      \\\ help me help AIDS victims -- http://ICCF-Holland.org ///

      --
      --
      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+unsubscribe@....
      For more options, visit https://groups.google.com/groups/opt_out.
    • raf
      ... it s fixed here too. thanks. cheers, raf -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you
      Message 36 of 36 , Jul 28, 2013
      • 0 Attachment
        Yukihiro Nakadaira wrote:

        > On Thu, Jul 25, 2013 at 12:53 AM, Bram Moolenaar <Bram@...> wrote:
        >
        > >
        > > Yukihiro Nakadaira wrote:
        > >
        > > > On Mon, Jul 8, 2013 at 9:51 AM, <raf@...> wrote:
        > > >
        > > > > Bram Moolenaar wrote:
        > > > >
        > > > > > Announcing: Vim (Vi IMproved) version 7.4a BETA
        > > > > >
        > > > > > This is the first BETA release of Vim 7.4.
        > > > > >
        > > > > > Please check that the distribution is OK. I haven't done one for a
        > > long
        > > > > > time. Report anything that isn't right. That includes a crash but
        > > also
        > > > > > a typo in the documentation or a missing file.
        > > > >
        > > > > mid-2010 macbookpro
        > > > > macosx-10.6.8
        > > > > gcc-4.2.1
        > > > >
        > > > > obtained vim-7.4a.002 via hg (same result via ftp).
        > > > >
        > > > > configure \
        > > > > --disable-darwin \
        > > > > --with-x \
        > > > > --enable-gui=motif \
        > > > > --enable-multibyte \
        > > > > --with-mac-arch=current \
        > > > > --with-features=huge \
        > > > > --disable-acl
        > > > >
        > > > > Test results:
        > > > > test96 FAILED
        > > > > TEST FAILURE
        > > > >
        > > > > diff -u test96.ok test96.failed
        > > > > --- test96.ok 2013-07-08 10:12:36.000000000 +1000
        > > > > +++ test96.failed 2013-07-08 10:15:31.000000000 +1000
        > > > > @@ -4,6 +4,8 @@
        > > > > - quickfix claims that the file name displayed is: test://bar.txt
        > > > > Test B:
        > > > > - number of window open: 2
        > > > > +Test B:
        > > > > + - number of window open: 2
        > > > > Test C:
        > > > > - 'buftype' of the location list window: quickfix
        > > > > - buffer displayed in the 2nd window: test://quux.txt
        > > > >
        > > > > i.e. the "Test B" section of the file is repeated.
        > > > >
        > > >
        > > > test96 failed on Windows Vista, too.
        > > >
        > > > Maybe I found the cause of this problem. test96 depends on cursor
        > > > position after switching buffer. But it is not stable. Try the
        > > > following script:
        > > >
        > > > call setline(1, range(10))
        > > > for i in range(5)
        > > > new
        > > > buffer 1
        > > > let &l:foldminlines = i
        > > > call cursor(i, 1)
        > > > endfor
        > > > for i in range(5)
        > > > quit
        > > > endfor
        > > > for i in range(5)
        > > > new
        > > > buffer 1
        > > > endfor
        > > >
        > > > Now, each window have different cursor position and different
        > > > window-local option value (&l:foldminlines in this case).
        > > >
        > > > I guess:
        > > > win_free() doesn't clear buf->b_wininfo.
        > > > After freeing memory, win_alloc() can return same address.
        > > > Then, buf->b_wininfo is re-used for newly allocated window in spite of
        > > > diffrent window.
        > >
        > > It would be possible. Unfortunately I could not reproduce the problem.
        > >
        > > Please check if patch 7.4a.044 fixes the problem.
        >
        >
        > The problem seems to be solved. Thank you.
        >
        > --
        > Yukihiro Nakadaira - yukihiro.nakadaira@...

        it's fixed here too. thanks.

        cheers,
        raf

        --
        --
        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+unsubscribe@....
        For more options, visit https://groups.google.com/groups/opt_out.
      Your message has been successfully submitted and would be delivered to recipients shortly.