From: John Keeping <john@keeping.me.uk>
To: Andreas Jacobsen <andreas@andreasjacobsen.com>
Cc: git@vger.kernel.org
Subject: Re: Segfault in git merge-tree (1.8.2.2)
Date: Mon, 6 May 2013 14:39:37 +0100 [thread overview]
Message-ID: <20130506133937.GB25912@serenity.lan> (raw)
In-Reply-To: <CADEJa-5prhhY-fUHgkk91M8HKWRG3enODS_h7Mq0dgo7V9sYsQ@mail.gmail.com>
On Mon, May 06, 2013 at 03:02:10PM +0200, Andreas Jacobsen wrote:
> I'm getting a segfault in git merge-tree using v1.8.2.2 on MacOS
> 10.8.3. I can't share the repo, but I can build patches and check if
> they fix the problem :)
Can you rebuild with debugging information and try the backtrace again?
Something like:
make CFLAGS='-O0 -g'
Then use the "git" in bin-wrappers/.
next prev parent reply other threads:[~2013-05-06 13:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-06 13:02 Segfault in git merge-tree (1.8.2.2) Andreas Jacobsen
2013-05-06 13:39 ` John Keeping [this message]
2013-05-06 14:13 ` Andreas Jacobsen
2013-05-06 14:29 ` John Keeping
2013-05-06 14:49 ` John Keeping
2013-05-06 15:20 ` [PATCH] merge-tree: handle directory/empty conflict correctly John Keeping
2013-05-07 4:54 ` Andreas Jacobsen
2013-05-07 5:17 ` 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=20130506133937.GB25912@serenity.lan \
--to=john@keeping.me.uk \
--cc=andreas@andreasjacobsen.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).