{"thread":{"id":"52640","subject":"See Fault when running git diff","startedAt":"2020-01-15T19:48:00Z","lastAt":"2020-03-28T17:08:49Z","messageCount":2,"participants":["Stewart, Tim","Philip Oakley"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"389814","messageId":"771f0c5de3874158acdeb18003ac62495F73D361-1387-42DA-B582-725ADA24BB21@pearson.com","threadId":"52640","inReplyTo":null,"subject":"See Fault when running git diff","fromName":"Stewart, Tim","fromEmail":"timothy.stewart@pearson.com","sentAt":"2020-01-15T19:47:55Z","receivedAt":"2020-01-15T19:48:00Z","isPatch":false,"sender":{"key":"timothy.stewart@pearson.com","avatar":null},"body":"\n\nHi, \n    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!\n \nGit Version: 2.25.0 (installed via homebrew on Mac OS X)\nHomebrew Version: 2.2.3\nMac OS version: 10.14.6 (18G2022)\nReproduced under zsh and sh shells.\n \nSteps to reproduce:\n\n\nStart a rebase operation that results in one or more conflicts in one or more of the repository’s sub-directories.\nList the conflicts with the following command: git diff --name-only --diff-filter=U –relative\nIdentify one of the conflicts that is in a subdirectory.\ncd to that directory\nRun the same command again: git diff --name-only --diff-filter=U –relative\nReceive segmentation fault error.  I would have expected to see a list of files relative to the current directory.\nThe 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):\ngit diff --name-only --diff-filter=U\ngit diff                        --diff-filter=U –relative\n\n\n \nIt 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.\n\n \nThanks!\n \n-- \n\n\n\n\n\n\nTim Stewart\n\nPrincipal Research Engineer\n\n\n\n\nIntelligent Systems R&D, AI Research Engineering\n\nAI Products & Solutions\n\n\n\n\n \nOffice:   +1 303.658.1505\nMobile: +1 303.912.2312\n \nBRAVE | IMAGINATIVE | DECENT | ACCOUNTABLE\nLearn more at www.pearson.com\n\n\n "},{"id":"394242","messageId":"11fa2daa-b301-6128-9f25-384a5ad7dc27@iee.email","threadId":"52640","inReplyTo":"771f0c5de3874158acdeb18003ac62495F73D361-1387-42DA-B582-725ADA24BB21@pearson.com","subject":"Re: See Fault when running git diff","fromName":"Philip Oakley","fromEmail":"philipoakley@iee.email","sentAt":"2020-03-28T17:08:46Z","receivedAt":"2020-03-28T17:08:49Z","isPatch":false,"sender":{"key":"philipoakley@iee.email","avatar":"https://avatars.githubusercontent.com/u/914343?v=4"},"body":"Hi Tim,\n\nOn 15/01/2020 19:47, Stewart, Tim wrote:\n> Steps to reproduce:\n>\n>\n> Start a rebase operation that results in one or more conflicts in one or more of the repository’s sub-directories.\n> List the conflicts with the following command: git diff --name-only --diff-filter=U –relative\n> Identify one of the conflicts that is in a subdirectory.\n> cd to that directory\n> Run the same command again: git diff --name-only --diff-filter=U –relative\n> Receive segmentation fault error.  I would have expected to see a list of files relative to the current directory.\n> 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):\n> git diff --name-only --diff-filter=U\n> git diff                        --diff-filter=U –relative\n>\n>\n>  \n> 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.\nIs this still present in the recent V2.26.0?\n--\nPhilip, (catching up on old emails)\n"}]}