git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
* See Fault when running git diff
@ 2020-01-15 19:47 Stewart, Tim
  2020-03-28 17:08 ` Philip Oakley
  0 siblings, 1 reply; 2+ messages in thread
From: Stewart, Tim @ 2020-01-15 19:47 UTC (permalink / raw)
  To: git@vger.kernel.org



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


 

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: See Fault when running git diff
  2020-01-15 19:47 See Fault when running git diff Stewart, Tim
@ 2020-03-28 17:08 ` Philip Oakley
  0 siblings, 0 replies; 2+ messages in thread
From: Philip Oakley @ 2020-03-28 17:08 UTC (permalink / raw)
  To: Stewart, Tim, git@vger.kernel.org

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)

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2020-03-28 17:08 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-01-15 19:47 See Fault when running git diff Stewart, Tim
2020-03-28 17:08 ` Philip Oakley

Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).