Guotuofeng wrote: > The full crash analyze is: > > Opened log file 'd:\gvimcrash.txt' > 0:000> k > ChildEBP RetAddr > 003bf2e8 776af5c9 ntdll!RtlReportCriticalFailure+0x29 > 003bf2f8 776af6a9 ntdll!RtlpReportHeapFailure+0x21 > 003bf32c 7766a5cb ntdll!RtlpLogHeapFailure+0xa1 > 003bf374 776135a7 ntdll!RtlpCoalesceFreeBlocks+0x84c > 003bf46c 77613492 ntdll!RtlpFreeHeap+0x1f4 > 003bf48c 62c2a25d ntdll!RtlFreeHeap+0x142 > 003bf4b0 75e414dd AcXtrnal!NS_FaultTolerantHeap::APIHook_RtlFreeHeap+0x3e5 > 003bf4c4 01121879 kernel32!HeapFree+0x14 > 003bf4d8 010bb385 gvim!free+0x1c > [f:\dd\vctools\crt_bld\self_x86\crt\src\free.c @ 51] > 003bf4e4 010bd09e gvim!free_screenlines+0xc > [k:\mercurial\vimcode\vim\src\screen.c @ 8210] > 003bf540 010bd1c6 gvim!screenalloc+0x5e2 > [k:\mercurial\vimcode\vim\src\screen.c @ 8138]
Don't see something special here. Can you run Vim with valgrind, then we can see what happens with allocated memory early. See ":help valgrind". -- If you feel lonely, try schizophrenia. /// Bram Moolenaar -- b...@moolenaar.net -- 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
