From: "Shawn O. Pearce" <spearce@spearce.org>
To: cpettitt <cpettitt@gmail.com>, Pierre Habouzit <madcoder@debian.org>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: git-fast-import segfaults
Date: Fri, 26 Oct 2007 02:53:01 -0400 [thread overview]
Message-ID: <20071026065301.GL14735@spearce.org> (raw)
In-Reply-To: <de47e4420710251729j5858481cg69146385a2ed798d@mail.gmail.com>
cpettitt <cpettitt@gmail.com> wrote:
> I'm seeing the following errors when I run git-fast-import (on Intel
> OSX) with some data from a git-p4 import:
...
> I believe these errors started showing up in commit
> b449f4cfc972929b638b90d375b8960c37790618. I did a bisect on
> fast-import.c and this was the first commit for that file that
> exhibits this bug with the input.
>
> I thought I would check with the list to see if this is a known issue
> before I spend time trying to dig into it.
It is a known issue. Someone else has reported the same thing,
and bisecting pointed at the same commit. But they weren't able
to supply their input data for debugging by Pierre or myself as it
was a private project and they haven't had a chance to attempt to
debug it on their own.
Any light you can shed on the problem would be most appreciated.
--
Shawn.
next prev parent reply other threads:[~2007-10-26 6:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <de47e4420710251726nb45a19fk15b3105b735a74f8@mail.gmail.com>
2007-10-26 0:29 ` git-fast-import segfaults cpettitt
2007-10-26 6:53 ` Shawn O. Pearce [this message]
2007-10-26 7:59 ` [PATCH] Fix regression in fast-import.c due to strbufs Pierre Habouzit
2007-10-26 16:39 ` cpettitt
2007-10-26 17:25 ` Pierre Habouzit
2007-10-29 2:59 ` Shun Kei Leung
2007-10-29 6:29 ` Pierre Habouzit
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=20071026065301.GL14735@spearce.org \
--to=spearce@spearce.org \
--cc=cpettitt@gmail.com \
--cc=git@vger.kernel.org \
--cc=madcoder@debian.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).