git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jay Soffian" <jaysoffian@gmail.com>
To: "Dane Jensen" <careo@fastmail.fm>
Cc: git@vger.kernel.org
Subject: Re: [Bug] Segfault in git status
Date: Thu, 21 Feb 2008 10:34:47 -0500	[thread overview]
Message-ID: <76718490802210734o43e7eb2fid3f4677d5570ac2a@mail.gmail.com> (raw)
In-Reply-To: <F8D3F7F0-3A98-4576-BD89-6E5C682B351C@fastmail.fm>

On Mon, Feb 18, 2008 at 3:36 AM, Dane Jensen <careo@fastmail.fm> wrote:
> Hi all-
>
>  Somehow I've managed to create a repository that causes git status to
>  segfault. To be honest, I'm not entirely sure how just yet. This comes
>  after a weekend of splitting a repository into two separate
>  repositories, filtering out a directory from one, and then creating
>  grafts in those repositories to skip commits that now change nothing.
>
>  This was in OS X 10.5.2 with git compiled from cf5c51e. Falling back
>  to 1.5.4.2 cleared it up, so with the help of git bisect I've narrowed
>  the bug down to cf55870.
>
>  I'll spend some time this week trying to find the exact point in my
>  filtering that git status went south and report back if I can
>  replicate it in a more-controlled test.

BTW - you should have a crash log in ~/Library/Logs/CrashReporter and
that should list the function in which the crash occurred.

j.

  parent reply	other threads:[~2008-02-21 15:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-18  8:36 [Bug] Segfault in git status Dane Jensen
2008-02-19  1:26 ` Junio C Hamano
2008-02-19 23:18   ` Dane Jensen
2008-02-21 15:34 ` Jay Soffian [this message]
2008-02-21 16:01 ` Pieter de Bie
2008-02-21 16:20   ` Jeff King
2008-02-21 16:53   ` Jay Soffian
2008-02-21 17:17     ` Pieter de Bie
2008-02-21 17:19     ` Dane Jensen

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=76718490802210734o43e7eb2fid3f4677d5570ac2a@mail.gmail.com \
    --to=jaysoffian@gmail.com \
    --cc=careo@fastmail.fm \
    --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).