From: Jeff King <peff@peff.net>
Date: Fri, 08 Mar 2013 21:28:31 GMT
Subject: Re: Memory corruption when rebasing with git version 1.8.1.5 on arch
Message-ID: <20130308212831.GA9217@sigill.intra.peff.net>
In-Reply-To: <5139D76D.80703@bernhard-posselt.com>

On Fri, Mar 08, 2013 at 01:19:57PM +0100, Bernhard Posselt wrote:

> Using valgrind gives me:
> 
> $ valgrind /usr/bin/git pull --rebasehttps://github.com/PatrickHeller/core.git  master
> ==5995== Memcheck, a memory error detector
> ==5995== Copyright (C) 2002-2012, and GNU GPL'd, by Julian Seward et al.
> ==5995== Using Valgrind-3.8.1 and LibVEX; rerun with -h for copyright info
> ==5995== Command: /usr/bin/git pull --rebasehttps://github.com/PatrickHeller/core.git  master
> ==5995==
> remote: Counting objects: 5, done.
> remote: Compressing objects: 100% (1/1), done.
> remote: Total 3 (delta 2), reused 3 (delta 2)
> Unpacking objects: 100% (3/3), done.
>  Fromhttps://github.com/PatrickHeller/core
>   * branch            master     -> FETCH_HEAD
> First, rewinding head to replay your work on top of it...
> Applying: distinguish between touch and write
> Applying: remove debug output
> *** Error in `git': malloc(): memory corruption: 0x00000000027f14e0 ***

The problem is likely happening in a sub-command of git-pull, so
valgrind isn't reporting it. Can you try re-running with
"valgrind --trace-children=yes", or alternatively narrow down the
problematic command by setting GIT_TRACE=1 in the environment?

-Peff