From: Andrew Wong <andrew.kw.w@gmail.com>
Date: Tue, 16 Oct 2012 20:12:12 GMT
Subject: Re: error: git-fast-import died of signal 11
Message-ID: <CADgNjanD=gYF_J7onuY6gK2mXuj1XGjWWX28nb2aAYPfmWH3PQ@mail.gmail.com>
In-Reply-To: <CAMJd5AR2gsyymKhT_hK9=4bHbcVnn+qEaDSxrZeJL1dfbmDxTw@mail.gmail.com>

On Tue, Oct 16, 2012 at 3:41 PM, Uri Moszkowicz <uri@4refs.com> wrote:
> I can do that if it still fails tomorrow. How do I build a debug version of git?
>
> On Tue, Oct 16, 2012 at 2:35 PM, Andrew Wong <andrew.kw.w@gmail.com> wrote:
>> Yea, it's a difficult problem to diagnose. It'd be really helpful if
>> you can run a debug version of git and run the import process under a
>> debugger.

After getting git's source, you can simply run "make", and it'll
compile with debug info by default. When compiling is done, you will
see all the binaries in the source's root folder. Then, from the
source folder, you can start gdb by the command:
    gdb ./git-fast-import

When you're inside gdb, put a breakpoint on "die_nicely" by entering:
    b die_nicely

Then, you can finally run your import process by entering:
    r < your_cvs_dump

When fast-import crashes/dies, you can find the stacktrace by entering:
    bt

And that should tell us where it crashed, and, hopefully, where the
memory error happened.