From: "Stewart, Tim" <Timothy.Stewart@Pearson.com>
To: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: See Fault when running git diff
Date: Wed, 15 Jan 2020 19:47:55 +0000 [thread overview]
Message-ID: <771f0c5de3874158acdeb18003ac62495F73D361-1387-42DA-B582-725ADA24BB21@pearson.com> (raw)
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
next reply other threads:[~2020-01-15 19:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-15 19:47 Stewart, Tim [this message]
2020-03-28 17:08 ` See Fault when running git diff Philip Oakley
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=771f0c5de3874158acdeb18003ac62495F73D361-1387-42DA-B582-725ADA24BB21@pearson.com \
--to=timothy.stewart@pearson.com \
--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.
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).