Here is the filled out form for submitting a bug report: What did you do before the bug happened? (Steps to reproduce your issue) At the command line, I typed the following command: $ git diff --no-index --word-diff --color=always <(od -An -t x1 -w10000000000 file1.txt) <(od -An -t x1 -w10000000000 file2.txt) What did you expect to happen? (Expected behavior) I expected to see the diff of the two files. What happened instead? (Actual behavior) Instead I saw this: error: Could not access '/proc/1961/fd/63' What's different between what you expected and what actually happened? The difference is that I would get the difference between the two files as opposed to a critical failure message. Anything else you want to add: Nope. Please review the rest of the bug report below. You can delete any lines you don't wish to share. [System Info] git version: git version 2.38.1.windows.1 cpu: x86_64 built from commit: b85c8f604d375d4d773a36842964e8a7ec056aae sizeof-long: 4 sizeof-size_t: 8 shell-path: /bin/sh feature: fsmonitor--daemon uname: Windows 10.0 19044 compiler info: gnuc: 12.2 libc info: no libc information available $SHELL (typically, interactive shell): C:\Program Files\Git\usr\bin\bash.exe [Enabled Hooks] not run from a git repository - no hooks to show
