From: Stefano Lattarini <stefano.lattarini@gmail.com>
To: Jason Gross <jasongross9@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: *** glibc detected *** git: double free or corruption (fasttop): 0x0000000001fab820 ***
Date: Tue, 04 Jun 2013 18:24:59 +0200 [thread overview]
Message-ID: <51AE14DB.6080505@gmail.com> (raw)
In-Reply-To: <CAKObCardgmTiuuE_LbzjD2fCmqwMHXbN-6-xZV_uUV=fjcBs3g@mail.gmail.com>
On 06/04/2013 05:46 PM, Jason Gross wrote:
> I get "*** glibc detected *** git: double free or corruption
> (fasttop): 0x0000000001fab820 ***" reliably on the following set of
> commands. I'm working on a remote machine where I don't have
> administrative privileges, so I can't update from git 1.7.2.5 to a
> newer version.
>
Sure you can; install from a release tarball. The page
<http://git-scm.com/downloads> links the latest version
(1.8.3) as well as older ones.
As for the issue you reported, I'll leave that to the real git
developers (I'm only a lurker here).
Regards,
Stefano
next prev parent reply other threads:[~2013-06-04 16:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-04 15:46 *** glibc detected *** git: double free or corruption (fasttop): 0x0000000001fab820 *** Jason Gross
2013-06-04 16:24 ` Stefano Lattarini [this message]
2013-06-04 16:26 ` Jeff King
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51AE14DB.6080505@gmail.com \
--to=stefano.lattarini@gmail.com \
--cc=git@vger.kernel.org \
--cc=jasongross9@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).