From: Bob Copeland <me@bobcopeland.com>
To: git@vger.kernel.org
Subject: segfault in http-push
Date: Sun, 17 Feb 2008 17:00:13 -0500 [thread overview]
Message-ID: <20080217220013.GA12419@hash.localnet> (raw)
Hi,
With 1.4.5.2, I see this whenever I try to push a new branch over http:
$ git-push hash long_ids
Fetching remote heads...
refs/
refs/heads/
refs/tags/
refs/remotes/
updating 'refs/heads/long_ids'
from 0000000000000000000000000000000000000000
to b24938890f04f3ba42b88f56f3ff2bbe0fda6629
sending 10200 objects
done
Updating remote server info
error: http-push died with strange error
error: failed to push to 'https://user@machine/foo.git/'
Here's a backtrace:
#0 0xb7cbd583 in strlen () from /lib/tls/i686/cmov/libc.so.6
#1 0x08053b5a in start_put (request=0xdce9ad8) at http-push.c:520
#2 0x080550d7 in fill_active_slot (unused=0x0) at http-push.c:810
#3 0x0804da9d in fill_active_slots () at http.c:428
#4 0x0804dc8b in step_active_slots () at http.c:454
#5 0x0804dd0b in run_active_slot (slot=0x8e70148) at http.c:474
#6 0x080502c9 in remote_ls (path=0x808bdbd "refs/", flags=5,
userFunc=0x804f2b0 <add_remote_info_ref>, userData=0xbfa04434)
at http-push.c:1467
#7 0x08050552 in update_remote_info_refs (lock=0x80e66c0) at http-push.c:1942
#8 0x080534ee in main (argc=3, argv=Cannot access memory at address 0x4
) at http-push.c:2421
Error is at:
520 request->url = xmalloc(strlen(remote->url) +
521 strlen(request->lock->token) + 51);
(gdb) p request->lock
$1 = (struct remote_lock *) 0x80e7d40
(gdb) p request->lock->token
$2 = 0x65707954 <Address 0x65707954 out of bounds>
If I go fix up the remote repository I can usually get it to work.
Any thoughts?
--
Bob Copeland %% www.bobcopeland.com
next reply other threads:[~2008-02-17 22:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-17 22:00 Bob Copeland [this message]
2008-02-17 23:23 ` segfault in http-push Johannes Schindelin
2008-02-18 2:05 ` Bob Copeland
2008-02-18 2:08 ` Johannes Schindelin
2008-02-18 3:06 ` Junio C Hamano
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=20080217220013.GA12419@hash.localnet \
--to=me@bobcopeland.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.