threads / discuss / 37082

Error running 'git status' with Git version of current 'next' branch

Subject: Error running 'git status' with Git version of current 'next' branch

## tl;dr

2 messages between Jul 9, 2014 and Jul 12, 2014.

replies: 1people: 2as markdown or json

Ralf Thielow· Jul 9, 2014, 07:10 UTC · lore

Hi,

I'm getting the following error when calling 'git status' on one of my projects.

git: dir.c:739: last_exclude_matching_from_list: Assertion `x->baselen == 0 || x->base[x->baselen - 1] == '/'' failed. Aborted (core dumped)

I'm using the current 'next', git version 2.0.1.664.g35b839c I have bisected it to commit d3ccb7d (dir: remove PATH_MAX limitation).

Here's a simple script to reproduce it:

mkdir tmp cd tmp git init mkdir -p foo/foooooooooo-bar/foooobar/foo/bar/foo/foobar/foooooooo/baaaaaar/fooooo echo /foo >foo/.gitignore git status

Ralf

Jeff King· Jul 12, 2014, 04:59 UTC · re: Ralf Thielow · lore

Re: Error running 'git status' with Git version of current 'next' branch

On Wed, Jul 09, 2014 at 09:10:49AM +0200, Ralf Thielow wrote:

Show 9 quoted lines

> I'm getting the following error when calling 'git status' on one of
> my projects.
> 
> git: dir.c:739: last_exclude_matching_from_list: Assertion `x->baselen
> == 0 || x->base[x->baselen - 1] == '/'' failed.
> Aborted (core dumped)
> 
> I'm using the current 'next', git version 2.0.1.664.g35b839c
> I have bisected it to commit d3ccb7d (dir: remove PATH_MAX limitation).

Thanks for bisecting. That commit has been reverted from next in favor of a nicer refactoring, though, so I don't think it's worth tracking down the bug in d3ccb7d.

-Peff