On 16/12/2015 15:28, Dominique Pellé wrote:
Mike Williams <[email protected]> wrote:
hg bisect to the rescue! The sort corruption starts with this commit of a
one line change:
changeset: 4791:65cef998f860
tag: v7.3.1142
user: Bram Moolenaar <[email protected]>
date: Fri Jun 07 19:48:39 2013 +0200
files: src/syntax.c src/version.c
description:
updated for version 7.3.1142
Problem: Memory leak in ":syntime report".
Solution: Clear the grow array. (Dominique Pelle)
Hi Mike
This looks strange to me:
- patch 7.3.1142 looks fine to me at first sight
- and the code changed in patch 7.3.1142 is not executed
anyway in the case described by John Beckett.
Can you or someone else double-check the bisection?
Unfortunately, I still cannot reproduce the bug myself.
I have checked it through again and it now looks unreliable. Builds I
swear worked ok before now fail when built again, and this is with clean
rebuilds each time. I can't go back that far in VIM history due to
limited compiler support in past years. If nothing else that would seem
to indicate the cause of the issue is not something recent.
I have started looking at DrMemory but there is a fair amount of
background noise, not least due to the NFA logs produced with debug
builds. It will take a little while to learn this tool.
Maybe someone also has access to proprietary tools
on Windows like Purify or Insure++.
Sorry, I don't. Anyone else?
Mike
--
Help support helpless victims of computer error.
--
--
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.
