[PATCH 4 of 6 v6 lazy-manifest] manifest: use custom C implementation of lazymanifest

[Matt Harbison]

On Sat, 07 Mar 2015 12:16:19 -0500, Augie Fackler <raf at durin42.com> wrote:

> # HG changeset patch
> # User Augie Fackler <augie at google.com>
> # Date 1425695387 18000
> #      Fri Mar 06 21:29:47 2015 -0500
> # Node ID 821f59a10986d380352d4f88f65f9398e3671d4e
> # Parent  74e64852b07f9cfb5a7b89d827dd9e1f01314b1b
> manifest: use custom C implementation of lazymanifest

I'm getting a python crash on Windows, starting with this when running  
'./run-tests.py --local test-locate.t', with 2.7.2.  Letting Visual Studio  
debug it only indicates that it dies in a free(), on top of a fairly large  
python27.dll call stack.

What's the best way to go about debugging this?  Is there a way to build  
the dll in debug mode, and maybe it will trigger some assertion closer to  
the original heap corruption?

--Matt