Christian Brabandt wrote: > On So, 12 Jun 2016, Bram Moolenaar wrote: > > > > > Patch 7.4.1926 > > Problem: Possible crash with many history items. > > Solution: Avoid the index going past the last item. > > Files: src/ex_getln.c > > Something between 7.4.1924 and 7.4.1926 broke the daily binary built: > > ..\gvim -u dos.vim -U NONE --noplugin --not-a-term "+set ff=dos|f > dostmp\test58.in|wq" test58.in > move test58.in test58.in.bak > 1 file(s) moved. > copy dostmp\test58.in test58.in > 1 file(s) copied. > copy test58.ok test.ok > 1 file(s) copied. > ..\gvim -u dos.vim -U NONE --noplugin --not-a-term -s dotest.in test58.in > NMAKE : fatal error U1077: '..\gvim.EXE' : return code '0xc0000005' > Stop. > > I rebuild that commit 3 times and it always breaks at that step for the > 32bit build. Does anybody know, what that means?
Strange. AppVeyor doesn't show a problem. I don't think there was a system-specific change recently (after the Ruby change). The changes for the viminfo improvements do a lot to arrays and tables which could cause memory access problems. I fixed several while testing the changes, there might be another one hiding. But running the tests with valgrind don't show problems. I'll see if running test58 shows something. -- >From "know your smileys": ...---... SOS /// Bram Moolenaar -- [email protected] -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
