# See Fault when running git diff

2 messages from 2020-01-15 to 2020-03-28. Participants: Stewart, Tim, Philip Oakley.
Thread: https://gitlist.dev/t/52640

## Stewart, Tim, 2020-01-15 19:47

Subject: See Fault when running git diff
Message-ID: <771f0c5de3874158acdeb18003ac62495F73D361-1387-42DA-B582-725ADA24BB21@pearson.com>
URL: https://gitlist.dev/e/771f0c5de3874158acdeb18003ac62495F73D361-1387-42DA-B582-725ADA24BB21%40pearson.com

```


Hi, 
    I’ve been using git for years and this is the first time I’ve ever seen a crash.  What a testament to the quality of the software you are developing!  Thank you!
 
Git Version: 2.25.0 (installed via homebrew on Mac OS X)
Homebrew Version: 2.2.3
Mac OS version: 10.14.6 (18G2022)
Reproduced under zsh and sh shells.
 
Steps to reproduce:


Start a rebase operation that results in one or more conflicts in one or more of the repository’s sub-directories.
List the conflicts with the following command: git diff --name-only --diff-filter=U –relative
Identify one of the conflicts that is in a subdirectory.
cd to that directory
Run the same command again: git diff --name-only --diff-filter=U –relative
Receive segmentation fault error.  I would have expected to see a list of files relative to the current directory.
The following commands work just fine in the subdirectory you cd’ed to (I introduced spacing to make which arguments are present or absent more clear):
git diff --name-only --diff-filter=U
git diff                        --diff-filter=U –relative


 
It appears that the –diff-filter=U argument is not required to induce the seg fault making the minimal failing case: ‘git diff --name-only –relative’ when run from a subdirectory.

 
Thanks!
 
-- 






Tim Stewart

Principal Research Engineer




Intelligent Systems R&D, AI Research Engineering

AI Products & Solutions




 
Office:   +1 303.658.1505
Mobile: +1 303.912.2312
 
BRAVE | IMAGINATIVE | DECENT | ACCOUNTABLE
Learn more at www.pearson.com


 
```

## Philip Oakley, 2020-03-28 17:08

Subject: Re: See Fault when running git diff
Message-ID: <11fa2daa-b301-6128-9f25-384a5ad7dc27@iee.email>
URL: https://gitlist.dev/e/11fa2daa-b301-6128-9f25-384a5ad7dc27%40iee.email
In-Reply-To: <771f0c5de3874158acdeb18003ac62495F73D361-1387-42DA-B582-725ADA24BB21@pearson.com>

```
Hi Tim,

On 15/01/2020 19:47, Stewart, Tim wrote:
> Steps to reproduce:
>
>
> Start a rebase operation that results in one or more conflicts in one or more of the repository’s sub-directories.
> List the conflicts with the following command: git diff --name-only --diff-filter=U –relative
> Identify one of the conflicts that is in a subdirectory.
> cd to that directory
> Run the same command again: git diff --name-only --diff-filter=U –relative
> Receive segmentation fault error.  I would have expected to see a list of files relative to the current directory.
> The following commands work just fine in the subdirectory you cd’ed to (I introduced spacing to make which arguments are present or absent more clear):
> git diff --name-only --diff-filter=U
> git diff                        --diff-filter=U –relative
>
>
>  
> It appears that the –diff-filter=U argument is not required to induce the seg fault making the minimal failing case: ‘git diff --name-only –relative’ when run from a subdirectory.
Is this still present in the recent V2.26.0?
--
Philip, (catching up on old emails)

```