From: Jeff King <peff@peff.net>
To: David Krmpotic <david.krmpotic@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Fwd: segmentation fault 11
Date: Sun, 8 Feb 2015 20:36:57 -0500 [thread overview]
Message-ID: <20150209013657.GC21072@peff.net> (raw)
In-Reply-To: <CAOFaZ+42Wbk8t_UmLGwxhRo+ZZOhpUT32o5wuj+LcJhaELOu5A@mail.gmail.com>
On Sun, Feb 08, 2015 at 06:56:14PM +0100, David Krmpotic wrote:
> I updated to 2.3.0 on my OSX 10.9.5 and when trying to push to github
> (git push -u origin master), I get:
>
> Segmentation fault: 11
>
> Switched back to 1.8.5.5 and it works...
Is this reproducible easily? If so, can you do one or both of:
1. Get a backtrace by running git-push under gdb (and/or loading gdb
on the core file if you have it). The report you linked mentions
that we were in "0x0000000102b70ebe cmd_push + 2466", but without
having your binary, that only gives a vague sense of the line
that caused the problem.
2. Bisect the bug between v1.8.5.5 and v2.3.0. I can walk you through
the specific steps if you've never bisected before.
Thanks.
-Peff
prev parent reply other threads:[~2015-02-09 1:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAOFaZ+5=bkWZpy1vFZjqMCgkWQySxGhLyfKhyH-VWDLJ28nTVQ@mail.gmail.com>
2015-02-08 17:56 ` Fwd: segmentation fault 11 David Krmpotic
2015-02-09 1:36 ` Jeff King [this message]
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=20150209013657.GC21072@peff.net \
--to=peff@peff.net \
--cc=david.krmpotic@gmail.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.