Avatar of phoffric
phoffric
 asked on

Gitk: Unable to see git differences for staged files

I have Windows 10 and Git Bash to get access to Git and Gitk on three platforms.


1. Office WS: Windows 10 Enterprise - git version 2.32.0.windows.1; gitk help - Copyright  TBD
2. Home PC: Windows 10 Home - git version 2.28.0.windows.1; gitk help - Copyright 2005-2016
3. Business Laptop: Windows 10 Pro - git version 2.33.0.windows.1; gitk help - Copyright 2005-2016


On platforms 1 and 2, when I hit the green circle  in gitk (i.e., staged files or aka files in the index), and select any of the staged files, the differences appear as expected.


But on platform 3, the differences do not appear for the staged files. On this platform, on gitk I only can see differences for files that are tracked but not staged (i.e., the red circle), or files that are committed. In the gitk difference pane, I just get see obvious message:
    "Local changes checked in to index but not committed"

How do I get gitk on platform 3 to display the staged differences like it does on the other two platforms.


The work-around is that in the git bash screen I type "git diff --staged" to see the differences.

GitProgrammingProgramming Languages-Other* gitk

Avatar of undefined
Last Comment
phoffric

8/22/2022 - Mon
David Favor

Seeing "Local changes checked in to index but not committed" (green dot)" requires your on the local machine where files have been changed.

File changes made locally at your office, are only known at your office... No where else in the... what... Git-o-spere (for lack of another word)... can see these changes.

Other's only learn of your changes after you commit your changes (checkin to the related repository), so this is likely working as designed.

You could somehow share a filesystem between your office + home, then you'd see the same detail both places.

At least this seems to be the logical way Git works.

I've never tried to seem my "uncommitted local changed files" anywhere else before... so someone else might have some trick to seeing uncommitted changed files.
phoffric

ASKER
@David,
I should have clarified..
 - I am only talking about local repositories.  No sharing is involved. This is just a gitk technical issue.
 - With that in mind..

>> Seeing "Local changes checked in to index but not committed" (green dot)" requires your on the local machine where files have been changed.
 - Yes, I agree, and that is the case.

>> File changes made locally at your office, are only known at your office
 - Yes, I agree, and that is the case.

>> Other's only learn of your changes after you commit your changes
 - Yes, I agree, and that would be true except that my office is disconnected from the internet.

>> You could somehow share a filesystem between...
  - No sharing is allowed.

>> someone else might have some trick to seeing uncommitted changed files.
  - To be clearer, I am talking about uncommitted changes that have been staged for commit (i.e., a git add operation was performed).
David Favor

This still seems to be working as designed.

Reading through the git docs, as I've never had cause to attempt what you're trying, still seems like staged changes can only be seen from the view of the single machine where a file has changed... never globally (all clients connected to a repository).

If you get stumped, with no comment here being useful, https://git-scm.com/community is the likely place you'll ask this question.
Your help has saved me hundreds of hours of internet surfing.
fblack61
phoffric

ASKER
>> This still seems to be working as designed

At the office, I can see the differences of the staged files in gitk.

I just want to setup gitk to act like it does in the office.


>> from the view of the single machine where a file has changed... never globally

You are missing the point that the operations are strictly local.

I rewrote the OP to make the question clearer.
Duncan Roe

I just tried gitk for the first time and, contrary to the man page, it created ~/.gitk as its config file.
Anyway, if you hunt around for your config files on your 2 PCs and diff them, you might see something.
Also check that you have the same rev of git on both systems.
phoffric

ASKER
Hi Duncan,
What do you use as a gitk alternative? At work, a lead recommended SourceTree by Atlassian, but that requires a license, and that makes it harder to get it in a closed office (i.e., no internet). At work I tried tortoiseGit for the first time, and it looked like it just showed all changes whether modified (red), or staged (green), and I did not see the red/green distinction. (But this was just a very quick look.)

When you went into gitk, did you try to see diffs of staged files?

On my home laptop, I did not find ~/.gitk, but I did find ~/.config/git/gitk. I'll check out the man pages and online searches to see if I can make sense of the parameters. Most of the file is related to fonts, colors, and geometry. Maybe "visiblerefs" is related to the problem. I remembered that I have another home PC that has bash on it. I'll see whether I can see diffs of staged files using its gitk, and then try to find a gitk config file.

I saw your post after I left work. I'll be back in the offic within two weeks.
set mainfont {Helvetica 12}
set textfont {Courier 12}
set uifont {Helvetica 9 bold}
set tabstop 3
set findmergefiles 0
set maxgraphpct 50
set maxwidth 16
set cmitmode patch
set wrapcomment none
set autoselect 1
set autosellen 40
set showneartags 1
set maxrefs 20
set visiblerefs {"master"}
set hideremotes 0
set showlocalchanges 1
set datetimeformat {%Y-%m-%d %H:%M:%S}
set limitdiffs 1
set uicolor SystemButtonFace
set want_ttk 1
set bgcolor SystemWindow
set fgcolor SystemWindowText
set uifgcolor SystemButtonText
set uifgdisabledcolor SystemDisabledText
set colors {"#00ff00" red blue magenta darkgrey brown orange}
set diffcolors {red #00a000 #4f4fff}
set mergecolors {red blue "#00ff00" purple brown "#009090" magenta "#808000" "#009000" "#ff0080" cyan "#b07070" "#70b0f0" "#70f0b0" "#f0b070" "#ff70b0"}
set markbgcolor #e0e0ff
set diffcontext 2
set selectbgcolor #1797ff
set foundbgcolor yellow
set currentsearchhitbgcolor orange
set extdifftool {C:/Program Files (x86)/Notepad++/notepad++.exe}
set perfile_attrs 0
set headbgcolor #00ff00
set headfgcolor black
set headoutlinecolor black
set remotebgcolor #ffddaa
set tagbgcolor yellow
set tagfgcolor black
set tagoutlinecolor black
set reflinecolor black
set filesepbgcolor #aaaaaa
set filesepfgcolor black
set linehoverbgcolor #ffff80
set linehoverfgcolor black
set linehoveroutlinecolor black
set mainheadcirclecolor yellow
set workingfilescirclecolor red
set indexcirclecolor #00ff00
set circlecolors {white blue gray blue blue}
set linkfgcolor blue
set circleoutlinecolor SystemWindowText
set diffbgcolors {"#fff3f3" "#f0fff0"}
set web_browser {cmd /c start}
set geometry(main) 2394x783+3349+89
set geometry(state) normal
set geometry(topwidth) 2394
set geometry(topheight) 288
set geometry(pwsash0) "1298 1"
set geometry(pwsash1) "1945 1"
set geometry(botwidth) 1407
set geometry(botheight) 490
set permviews {}

Open in new window

Changing gitk Preferences in the GUI (and exiting) causes this gitk file to be altered.
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.
Duncan Roe

Hi phoffric,

I use git status to see what's staged and what's not (the same file can be in both lists). git diff shows the red ones, to see the green ones as well git diff current-branch. Being rather slow at typing, I have aliases for most common commands
GB is aliased to `git branch'
GC is aliased to `git checkout'
GD is aliased to `git diff'
GDW is aliased to `git diff --word-diff'
GL is aliased to `git log'
GLP is aliased to `git log --all --graph --decorate --oneline'
GR is aliased to `git reset HEAD'
GS is aliased to `git status'

Open in new window

GLP is really neat especially if you have lots of branches (over 80 of them in one of my projects).

I only started gitk to get its default config file. Didn't spend long looking - too complicated for me;)
In my last job before retiring we used git on Windows latterly. Rather than use git bash, I used git from Cygwin which I had installed already for other GNU tools (and the Q editor). Cygwin mintty terminals are very much like xterms, so no need to mess about with GUIs.

The purpose of .gitk (or whatever) is to preserve settings between sessions. When I compared my default file with yours (after sorting them both!) I could only see GUI plus Windows/Linux diffs, except tabstop went from 8 to 3. There are interesting settings that were common including showlocalchanges and showneartags.
I still maintain that if you are seeing different behaviour at home and at work then it has to be config file or software revision.
Cheers ... Duncan.
phoffric

ASKER
Thanks for the git aliases.

Forgot that I had git on a PC, and gitk works fine on it. Its version is 2.28.0.windows.1 - installed this older version about a year ago.
Got latest "Git for Windows" in July, this year.

Compared gitk files; no differences that relate to cached (aka, staged; aka indexed) files.

Replaced the gitk in my laptop with the gitk file in the PC. The fonts were different but the OP problem still remains.

I skimmed through this link, but could not find the switch to toggle the behavior.

Maybe you are right that the newer git version I have has changed behavior that affects gitk. Or maybe it is one of the hundreds of config options. I may give up, or find a gitk forum.

BTW, I just ran Git Gui, and it does show staged and un-staged differences. I just wanted everything in one place along with the other items shown in gitk. I may drop this discussion for awhile, and find a gitk forum.
Duncan Roe

gitk is its own project: git clone git://ozlabs.org/~paulus/gitk
My distro (Slackware) appears to take the current gitk from that repository (last modified Sat Oct 3 15:20:33 2020 +1000)
The repo has gitk itself and what looks like some i8n stuff. Slackware diffs identical to gitk in the repo.
gitk is a text file - you can try your work version at home.
Only other config I can think of that might make a difference is ~/.gitconfig
All of life is about relationships, and EE has made a viirtual community a real community. It lifts everyone's boat
William Peck
phoffric

ASKER
Thanks for looking around. I was just hoping for a simple fix. I might try reinstalling git to see if that helps.  I think I used different starting points in both platforms.
Duncan Roe

After installing the latest gitk from ~paulus, I seegood.pdf
There is 1 uncommitted change which is to a staged file. If I click red dot I see diff for that file from the staged version.  If I click the green dor I see diff from HEAD to staged. I could not find an option to see diffs from HEAD to uncommitted change - is that what you wanted?
phoffric

ASKER
What you saw is fine. That is what I get on my PC. On my business laptop, when I click on the green dot, I do not see any differences. I just see the obvious:
"Local changes checked in to index but not committed"
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.
SOLUTION
Duncan Roe

Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
Sign up - Free for 7 days
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a question
phoffric

ASKER
(I updated the OP to reflect the clarifications we made.)
I copied the gitk and .gitconfig files from platform 2 (Home PC) to platform 3 (Business Laptop). The Home PC .gitconfig file only had email and name information.
The .gitconfig in the Business Laptop had settings to affect the git difftool command to invoke WinMerge instead of vim.
Still no luck.

Maybe I need to reboot to remove some cache.

Next step probably this weekend is to reinstall a new git. I may need to go back a few versions since I identify older git versions in the OP where gitk works with diffs of the staged files.
Duncan Roe

When I click on the green dot I see staged diffs straight away. If I turn off "View local changes" then they don't appear.
Local changes were on in the config file you posted - weird.
SOLUTION
Log in to continue reading
Log In
Sign up - Free for 7 days
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.
phoffric

ASKER
If not the git version, then yeah, some system-wide .gitconfig param is messing me up. I only know of two files that have git and gitk config params in them.. .gitconfig, and gitk for git and gitk, respectfully.
Experts Exchange has (a) saved my job multiple times, (b) saved me hours, days, and even weeks of work, and often (c) makes me look like a superhero! This place is MAGIC!
Walt Forbes
SOLUTION
Log in to continue reading
Log In
Sign up - Free for 7 days
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.
phoffric

ASKER
How did you instrument gitk to display all the git commands it issues?
Duncan Roe

Patched it by hand. Took a bit longer than initially expected (how unusual:) - almost a day. Did consider giving up and just using strace but the instrumentation is a little more informative.
Have you tried the commands yet?
phoffric

ASKER
OMG >> Patched it by hand. Took a bit longer than initially expected (how unusual:) - almost a day.
I didn't mean for you to spend so much time on this. :(

Am I hearing you right - You edited the gitk source code and rebuilt gitk?? If so, after all that work, you could add your gitk debug feature to github, I suppose.

As far as git corruption, you suggest doing another clone. I have about 5 local repos pointing to different shared repos. Gitk does not show diffs for staged files on any of them on my business laptop.

Could you please advise what bash command strace line I should use to see the gitk commands.
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.
SOLUTION
Log in to continue reading
Log In
Sign up - Free for 7 days
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.
phoffric

ASKER
Well, I do not blame you for not being the first to update gitk after 5 years.

In git bash, Line 2 produced 13 files that corresponded the green staged files shown in a git status.
But Line 3, not so good. This git diff-index is outside of my understanding of git. Given this is a pretty low priority item for me, I am happy to skip this step and just try a reinstallation of git. Likewise, now that I understand that gitk is a Tcl/Tk script, I must forgo learning that since that is getting way outside my current domain of career changing intensive study.

Maybe you see a typo?
$ git --version
git version 2.33.0.windows.1
$ git diff-index --cached -p --textconv --submodule -C --cc --no-commit-id -U3 --ignore-submodules=dirty HEAD
usage: git diff-index [-m] [--cached] [<common-diff-options>] <tree-ish> [<path>...]
common diff options:
  -z            output diff-raw with lines terminated with NUL.
  -p            output patch format.
  -u            synonym for -p.
  --patch-with-raw
                output both a patch and the diff-raw format.
  --stat        show diffstat instead of patch.
  --numstat     show numeric diffstat instead of patch.
  --patch-with-stat
                output a patch and prepend its diffstat.
  --name-only   show only names of changed files.
  --name-status show names and status of changed files.
  --full-index  show full object name on index lines.
  --abbrev=<n>  abbreviate object names in diff-tree header and diff-raw.
  -R            swap input file pairs.
  -B            detect complete rewrites.
  -M            detect renames.
  -C            detect copies.
  --find-copies-harder
                try unchanged files as candidate for copy detection.
  -l<n>         limit rename attempts up to <n> paths.
  -O<file>      reorder diffs according to the <file>.
  -S<string>    find filepair whose only one side contains the string.
  --pickaxe-all
                show all files diff when -S is used and hit is found.
  -a  --text    treat all files as text.

Open in new window

phoffric

ASKER
$ ps
      PID    PPID    PGID     WINPID   TTY         UID    STIME COMMAND
     1718       1    1718       4916  ?           4096   Oct 12 /usr/bin/mintty
     2654    1719    2654      19036  pty0        4096 17:34:13 /usr/bin/ps
     1719    1718    1719      24536  pty0        4096   Oct 12 /usr/bin/bash
     2648    1719    2648      10128  pty0        4096 17:34:07 /mingw64/bin/wish
$
$ strace -f -e execve -p $(1719)
bash: 1719: command not found
strace.exe: error creating process execve, (error 2)
$
$ strace -f -e execve -p $(2648)
bash: 2648: command not found
strace.exe: error creating process execve, (error 2)

Open in new window

Only time I get some interation from strace (which I do not know how it will help) is:

$ strace -p 2935
...  // strace initialization

     // click on the green staged dot
.appcore.dll at 00007ffb64630000
--- Process 18508 (pid: 2935) loaded C:\Windows\System32\bcryptprimitives.dll at 00007ffb66fd0000
--- Process 18508 (pid: 2935) loaded C:\Windows\System32\TextInputFramework.dll at 00007ffb56790000
--- Process 18508 (pid: 2935) loaded C:\Windows\System32\CoreUIComponents.dll at 00007ffb63670000
--- Process 18508 (pid: 2935) loaded C:\Windows\System32\CoreMessaging.dll at 00007ffb639d0000
--- Process 18508 (pid: 2935) loaded C:\Windows\System32\ntmarta.dll at 00007ffb65420000
--- Process 18508 (pid: 2935) loaded C:\Windows\System32\WinTypes.dll at 00007ffb62ec0000
--- Process 18508 (pid: 2935) thread 7748 created
--- Process 18508 (pid: 2935) thread 7748 exited with status 0x0
--- Process 18508 (pid: 2935) thread 23532 created
--- Process 18508 (pid: 2935) thread 18944 created
--- Process 18508 (pid: 2935) thread 5616 created
--- Process 10892 created
--- Process 10892 loaded C:\Windows\System32\ntdll.dll at 00007ffb69330000
--- Process 10892 loaded C:\Windows\System32\kernel32.dll at 00007ffb68ec0000
--- Process 10892 loaded C:\Windows\System32\KernelBase.dll at 00007ffb66b50000
--- Process 10892 loaded C:\Program Files\SentinelOne\Sentinel Agent 21.7.1.240\InProcessClient64.dll at 00007ffb665f0000
--- Process 10892 loaded C:\Windows\System32\advapi32.dll at 00007ffb67c60000
--- Process 10892 loaded C:\Windows\System32\msvcrt.dll at 00007ffb69250000
--- Process 10892 thread 19116 created
--- Process 10892 loaded C:\Windows\System32\sechost.dll at 00007ffb68780000
--- Process 10892 loaded C:\Windows\System32\rpcrt4.dll at 00007ffb673e0000
--- Process 10892 thread 24708 created
--- Process 10892 thread 6088 created
--- Process 10892 loaded C:\Windows\System32\user32.dll at 00007ffb68820000
--- Process 10892 loaded C:\Windows\System32\win32u.dll at 00007ffb672c0000
--- Process 10892 loaded C:\Program Files\Git\mingw64\bin\libiconv-2.dll at 00007ffb431c0000
--- Process 10892 loaded C:\Program Files\Git\mingw64\bin\libpcre2-8-0.dll at 00007ffb42ce0000
--- Process 10892 loaded C:\Program Files\Git\mingw64\bin\libintl-8.dll at 00007ffb5ea50000
--- Process 10892 loaded C:\Windows\System32\gdi32.dll at 00007ffb68140000
--- Process 10892 loaded C:\Windows\System32\gdi32full.dll at 00007ffb67060000
--- Process 10892 loaded C:\Program Files\Git\mingw64\bin\zlib1.dll at 00007ffb60a60000
--- Process 10892 loaded C:\Windows\System32\msvcp_win.dll at 00007ffb67220000
--- Process 10892 loaded C:\Windows\System32\ucrtbase.dll at 00007ffb66a50000
--- Process 10892 loaded C:\Windows\System32\ws2_32.dll at 00007ffb686a0000
--- Process 10892 loaded C:\Program Files\Git\mingw64\bin\libssp-0.dll at 00007ffb573d0000
--- Process 10892 loaded C:\Windows\System32\version.dll at 00007ffb665e0000
--- Process 10892 loaded C:\Windows\System32\imm32.dll at 00007ffb69170000
--- Process 10892 loaded C:\Windows\System32\cryptsp.dll at 00007ffb661e0000
--- Process 10892 loaded C:\Windows\System32\rsaenh.dll at 00007ffb657f0000
--- Process 10892 loaded C:\Windows\System32\bcrypt.dll at 00007ffb67350000
--- Process 10892 loaded C:\Windows\System32\cryptbase.dll at 00007ffb66200000
--- Process 10892 loaded C:\Windows\System32\bcryptprimitives.dll at 00007ffb66fd0000
--- Process 10892 thread 6088 exited with status 0x0
--- Process 10892 thread 24708 exited with status 0x0
--- Process 10892 thread 19116 exited with status 0x0
--- Process 10892 exited with status 0x0
--- Process 18508 (pid: 2935) thread 5616 exited with status 0x0
--- Process 18508 (pid: 2935) thread 9804 created
--- Process 23032 created
--- Process 23032 loaded C:\Windows\System32\ntdll.dll at 00007ffb69330000
--- Process 23032 loaded C:\Windows\System32\kernel32.dll at 00007ffb68ec0000
--- Process 23032 loaded C:\Windows\System32\KernelBase.dll at 00007ffb66b50000
--- Process 23032 loaded C:\Program Files\SentinelOne\Sentinel Agent 21.7.1.240\InProcessClient64.dll at 00007ffb665f0000
--- Process 23032 loaded C:\Windows\System32\advapi32.dll at 00007ffb67c60000
--- Process 23032 loaded C:\Windows\System32\msvcrt.dll at 00007ffb69250000
--- Process 23032 thread 2


     // click on the red modified but not staged dot
4156 created
--- Process 23032 loaded C:\Windows\System32\sechost.dll at 00007ffb68780000
--- Process 23032 loaded C:\Windows\System32\rpcrt4.dll at 00007ffb673e0000
--- Process 23032 thread 21016 created
--- Process 23032 thread 18912 created
--- Process 23032 loaded C:\Windows\System32\user32.dll at 00007ffb68820000
--- Process 23032 loaded C:\Windows\System32\win32u.dll at 00007ffb672c0000
--- Process 23032 loaded C:\Windows\System32\gdi32.dll at 00007ffb68140000
--- Process 23032 loaded C:\Program Files\Git\mingw64\bin\libiconv-2.dll at 00007ffb431c0000
--- Process 23032 loaded C:\Program Files\Git\mingw64\bin\libintl-8.dll at 00007ffb5ea50000
--- Process 23032 loaded C:\Windows\System32\gdi32full.dll at 00007ffb67060000
--- Process 23032 loaded C:\Program Files\Git\mingw64\bin\libpcre2-8-0.dll at 00007ffb42ce0000
--- Process 23032 loaded C:\Windows\System32\msvcp_win.dll at 00007ffb67220000
--- Process 23032 loaded C:\Windows\System32\ucrtbase.dll at 00007ffb66a50000
--- Process 23032 loaded C:\Program Files\Git\mingw64\bin\zlib1.dll at 00007ffb60a60000
--- Process 23032 loaded C:\Windows\System32\ws2_32.dll at 00007ffb686a0000
--- Process 23032 loaded C:\Program Files\Git\mingw64\bin\libssp-0.dll at 00007ffb573d0000
--- Process 23032 loaded C:\Windows\System32\version.dll at 00007ffb665e0000
--- Process 23032 loaded C:\Windows\System32\imm32.dll at 00007ffb69170000
--- Process 23032 loaded C:\Windows\System32\cryptsp.dll at 00007ffb661e0000
--- Process 23032 loaded C:\Windows\System32\rsaenh.dll at 00007ffb657f0000
--- Process 23032 loaded C:\Windows\System32\bcrypt.dll at 00007ffb67350000
--- Process 23032 loaded C:\Windows\System32\cryptbase.dll at 00007ffb66200000
--- Process 23032 loaded C:\Windows\System32\bcryptprimitives.dll at 00007ffb66fd0000
--- Process 23032 thread 21016 exited with status 0x81
--- Process 23032 thread 18912 exited with status 0x81
--- Process 23032 thread 24156 exited with status 0x81
--- Process 23032 exited with status 0x81
--- Process 18508 (pid: 2935) thread 9804 exited with status 0x0
--- Process 18508 (pid: 2935) thread 8712 created
--- Process 21776 created
--- Process 21776 loaded C:\Windows\System32\ntdll.dll at 00007ffb69330000
--- Process 21776 loaded C:\Windows\System32\kernel32.dll at 00007ffb68ec0000
--- Process 21776 loaded C:\Windows\System32\KernelBase.dll at 00007ffb66b50000
--- Process 21776 loaded C:\Program Files\SentinelOne\Sentinel Agent 21.7.1.240\InProcessClient64.dll at 00007ffb665f0000
--- Process 21776 loaded C:\Windows\System32\advapi32.dll at 00007ffb67c60000
--- Process 21776 loaded C:\Windows\System32\msvcrt.dll at 00007ffb69250000
--- Process 21776 thread 9640 created
--- Process 21776 loaded C:\Windows\System32\sechost.dll at 00007ffb68780000
--- Process 21776 loaded C:\Windows\System32\rpcrt4.dll at 00007ffb673e0000
--- Process 21776 thread 21980 created
--- Process 21776 thread 2904 created
--- Process 21776 loaded C:\Windows\System32\user32.dll at 00007ffb68820000
--- Process 21776 loaded C:\Windows\System32\win32u.dll at 00007ffb672c0000
--- Process 21776 loaded C:\Program Files\Git\mingw64\bin\libiconv-2.dll at 00007ffb431c0000
--- Process 21776 loaded C:\Program Files\Git\mingw64\bin\libpcre2-8-0.dll at 00007ffb42ce0000
--- Process 21776 loaded C:\Program Files\Git\mingw64\bin\libintl-8.dll at 00007ffb5ea50000
--- Process 21776 loaded C:\Windows\System32\gdi32.dll at 00007ffb68140000
--- Process 21776 loaded C:\Windows\System32\gdi32full.dll at 00007ffb67060000
--- Process 21776 loaded C:\Program Files\Git\mingw64\bin\zlib1.dll at 00007ffb60a60000
--- Process 21776 loaded C:\Windows\System32\msvcp_win.dll at 00007ffb67220000
--- Process 21776 loaded C:\Windows\System32\ucrtbase.dll at 00007ffb66a50000
--- Process 21776 loaded C:\Windows\System32\ws2_32.dll at 00007ffb686a0000
--- Process 21776 loaded C:\Program Files\Git\mingw64\bin\libssp-0.dll at 00007ffb573d0000
--- Process 21776 loaded C:\Windows\System32\version.dll at 00007ffb665e0000
--- Process 21776 loaded C:\Windows\System32\imm32.dll at 00007ffb69170000
--- Process 21776 loaded C:\Windo

Open in new window

The following produced no output:
$ strace -f -e -p 2994

Open in new window

Always get an error when using execve.
$ strace -f -e execve  -p 3026
strace.exe: error creating process execve, (error 2)

Open in new window

phoffric

ASKER
I started pruning the command line and got a huge amount of green and red diffs coming out.
git diff-index --cached -p  -C --no-commit-id -U3 --ignore-submodules=dirty HEAD

Open in new window

Above command is a one shot deal. Clicking on gitk green or red or yellow or blue dots produce nothing.
Experts Exchange is like having an extremely knowledgeable team sitting and waiting for your call. Couldn't do my job half as well as I do without it!
James Murphy
ASKER CERTIFIED SOLUTION
Log in to continue reading
Log In
Sign up - Free for 7 days
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.
phoffric

ASKER
Line 3 works now after uninstalling and reinstalling git. Thank you so much!!