From: "Shawn O. Pearce" <spearce@spearce.org>
To: Brian Gernhardt <brian@gernhardtsoftware.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: t5541-http-push hanging
Date: Wed, 11 Nov 2009 20:49:06 -0800 [thread overview]
Message-ID: <20091112044906.GQ11919@spearce.org> (raw)
In-Reply-To: <B17AB159-E217-4E1F-BEA3-97E5892C13F4@gernhardtsoftware.com>
Brian Gernhardt <brian@gernhardtsoftware.com> wrote:
> My build script for git has been hanging at t5541.2 and I haven't had the tuits to discover why. Here's what I've gotten so far, in case anyone can figure it out faster:
...
> git clone $HTTPD_URL/smart/test_repo.git test_repo_clone
...
> [Wed Nov 11 06:19:39 2009] [error] [client 127.0.0.1] git-http-backend(59490) malloc: *** error for object 0x100200340: incorrect checksum for freed object - object was probably modified after being freed.
> [Wed Nov 11 06:19:39 2009] [error] [client 127.0.0.1] *** set a breakpoint in malloc_error_break to debug
I can't reproduce this on 10.5.8. Can you try running it in the
debugger and putting a breakpoint where they suggest? Maybe it
will help give us some context information:
REQUEST_METHOD=GET \
PATH_TRANSLATED=`pwd`/.git/info/refs \
QUERY_STRING=service=git-upload-pack \
gdb ./git-http-backend
b malloc_error_break
run
I suspect that's where our failure is, the code path for the actual
common negotiation and data transfer is shorter, and less likely
to need to do a memory allocation... and therefore a free.
--
Shawn.
next prev parent reply other threads:[~2009-11-12 4:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-11 6:28 t5541-http-push hanging Brian Gernhardt
2009-11-11 15:47 ` Tay Ray Chuan
2009-11-11 16:53 ` Brian Gernhardt
2009-11-11 15:50 ` Shawn O. Pearce
2009-11-12 4:26 ` Shawn O. Pearce
2009-11-12 4:49 ` Shawn O. Pearce [this message]
2009-11-12 5:18 ` Brian Gernhardt
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=20091112044906.GQ11919@spearce.org \
--to=spearce@spearce.org \
--cc=brian@gernhardtsoftware.com \
--cc=git@vger.kernel.org \
/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).