Memory corruption when rebasing with git version 1.8.1.5 on arch
- From
- Bernhard Posselt <mail@bernhard-posselt.com>
- Date
- Mar 8, 2013, 12:19 UTC
- Message-ID
- <5139D76D.80703@bernhard-posselt.com>
Hi im running arch linux and core/glibc 2.17-3
When i try to rebase with:
git clonehttps://github.com/owncloud/core.git cd core/ git pull --rebasehttps://github.com/PatrickHeller/core.git master
I'm getting:
$ git pull --rebasehttps://github.com/PatrickHeller/core.git master 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: 0x0000000000be14e0 ***
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 ***
^C==5995== ==5995== HEAP SUMMARY: ==5995== in use at exit: 1,076 bytes in 11 blocks ==5995== total heap usage: 53 allocs, 42 frees, 11,038 bytes allocated ==5995== ==5995== LEAK SUMMARY: ==5995== definitely lost: 0 bytes in 0 blocks ==5995== indirectly lost: 0 bytes in 0 blocks ==5995== possibly lost: 0 bytes in 0 blocks