misterious GIT failure

[Cygwin list mailing list]

I've been using cygwin since like 20 years ago and do everything in it. A couple days ago my Git program mysteriously stopped working. I can see (GIT_TRACE=1) it invoke SSH and HTTPS connections just fine but it fails with a short-read/write when it's time for pack or unpack. Baffled I uninstalled Cygwin and blew away the Repo and started over. Git worked fine for a few hours and then BAM same problem. I've tried all three versions of git available in the repos. Short of deleting Cygwin entirely and starting over, nothing brings it back.

I use Github, Bitbucket, and CodeCommit (amazon) for various repositories and once Git stops working it won't work on any of them. (I briefly thought maybe there was some badly behaved backends)

Here's an example output. Anyone have a notion as to what the dickens is going on?

21:04:24.233957 git.c:444               trace: built-in: git fetch
21:04:24.238648 run-command.c:664       trace: run_command: unset GIT_PREFIX; GIT_PROTOCOL=version=2 ssh -o SendEnv=GIT_PROTOCOL [hidden email] 'git-upload-pack '\''tb3088/shell-environment.git'\'''
remote: Enumerating objects: 34, done.
remote: Counting objects: 100% (34/34), done.
remote: Compressing objects: 100% (25/25), done.
21:04:25.119943 run-command.c:664       trace: run_command: git index-pack --stdin -v --fix-thin '--keep=fetch-pack 1011 on SOHO-GP4D633' --pack_header=2,1635
fatal: index-pack failed

--
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple

[Adam Dinwoodie-2]

On Friday 08 January 2021 at 02:13 am +0000, matthew patton via Cygwin wrote:

> I've been using cygwin since like 20 years ago and do everything in
> it. A couple days ago my Git program mysteriously stopped working. I
> can see (GIT_TRACE=1) it invoke SSH and HTTPS connections just fine
> but it fails with a short-read/write when it's time for pack or
> unpack. Baffled I uninstalled Cygwin and blew away the Repo and
> started over. Git worked fine for a few hours and then BAM same
> problem. I've tried all three versions of git available in the repos.
> Short of deleting Cygwin entirely and starting over, nothing brings it
> back.
>
> I use Github, Bitbucket, and CodeCommit (amazon) for various
> repositories and once Git stops working it won't work on any of them.
> (I briefly thought maybe there was some badly behaved backends)
>
> Here's an example output. Anyone have a notion as to what the dickens is going on?
>
> 21:04:24.233957 git.c:444               trace: built-in: git fetch
> 21:04:24.238648 run-command.c:664       trace: run_command: unset GIT_PREFIX; GIT_PROTOCOL=version=2 ssh -o SendEnv=GIT_PROTOCOL [hidden email] 'git-upload-pack '\''tb3088/shell-environment.git'\'''
> remote: Enumerating objects: 34, done.
> remote: Counting objects: 100% (34/34), done.
> remote: Compressing objects: 100% (25/25), done.
> 21:04:25.119943 run-command.c:664       trace: run_command: git index-pack --stdin -v --fix-thin '--keep=fetch-pack 1011 on SOHO-GP4D633' --pack_header=2,1635
> fatal: index-pack failed

This looks like some sort of problem writing to disk to me.  Where are
you storing your Git repositories?  Is it on a regular NTFS disk, or a
file share, or something more esorteric?  And does that drive have
plenty of free space?

Can you please provide the cygcheck output per
https://cygwin.com/problems.html?

If neither of these points at an obvious problem, I expect the next step
will be either (a) looking at Cygwin strace output to get a more
detailed view of what's happening when things go wrong, or (b) having
you build and run the full Git test suite with a view to using that to
narrow down what steps are going wrong.

Adam
--
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple

[Achim Gratz]

matthew patton via Cygwin writes:
> I've been using cygwin since like 20 years ago and do everything in
> it. A couple days ago my Git program mysteriously stopped working. I
> can see (GIT_TRACE=1) it invoke SSH and HTTPS connections just fine
> but it fails with a short-read/write when it's time for pack or
> unpack. Baffled I uninstalled Cygwin and blew away the Repo and
> started over. Git worked fine for a few hours and then BAM same
> problem.

That seems to indicate some sort of behavioral based firewalling or IDS
rather than a problem in Cygwin.


Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptations for KORG EX-800 and Poly-800MkII V0.9:
http://Synth.Stromeko.net/Downloads.html#KorgSDada
--
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple

[Cygwin list mailing list]

Adam Dinwoodie wrote:> This looks like some sort of problem writing to disk to me.  Where are> you storing your Git repositories?  Is it on a regular NTFS disk
plain NTFS (win10 exterprise) with hundreds of GB free. I blew away contents of /tmp just to make sure it wasn't something silly going on there. It's git pack/unpack aborting the read/write from the pipe which causes SSH to then close and tear down the connection. SSH client helpfully provides stats on how many packets transferred up/down.
Achim Gratz wrote:> That seems to indicate some sort of behavioral based firewalling or IDS
I thought it could be that too. Tried with and without corporate VPN. But it's worked for over a year with this config and nary a hiccup. And anyway if I immediately switch to my WSL (Ubuntu) window or Git-Bash and issue the Git commands they run perfectly. Yes my Cygwin and WSL and Git-Bash share the exact same repository directories.
If I blow away the entire Cygwin installation (c:\cygwin64) and re-install Cygwin Git it will resume working and do so for a while. Like I mentioned previously re-installing Git does not solve the issue. And yes my SSH sessions while Git is "broken" continue to work like a champ, so it's not SSH.
I've attached cygcheck. Before I even posted I went looking for strace() to no avail. I also even did a manual connection attempt like this:    ssh blah | git index-pack --stdin -v --fix-thin '--keep=fetch-pack 1011 on SOHO-GP4D633' --pack_header=2,1635
and it would fail in the same manner as when it had been invoked "normally".

--
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple

[Andrey Repin]

Greetings, matthew patton!

> Adam Dinwoodie wrote:
>> This looks like some sort of problem writing to disk to me.  Where are
>> you storing your Git repositories?  Is it on a regular NTFS disk

> plain NTFS (win10 exterprise) with hundreds of GB free. I blew away
> contents of /tmp just to make sure it wasn't something silly going on there.
> It's git pack/unpack aborting the read/write from the pipe which causes SSH
> to then close and tear down the connection. SSH client helpfully provides
> stats on how many packets transferred up/down.

> Achim Gratz wrote:
>> That seems to indicate some sort of behavioral based firewalling or IDS

> I thought it could be that too. Tried with and without corporate VPN. But
> it's worked for over a year with this config and nary a hiccup. And anyway
> if I immediately switch to my WSL (Ubuntu) window or Git-Bash and issue the
> Git commands they run perfectly. Yes my Cygwin and WSL and Git-Bash share
> the exact same repository directories.
> If I blow away the entire Cygwin installation (c:\cygwin64) and re-install
> Cygwin Git it will resume working and do so for a while. Like I mentioned
> previously re-installing Git does not solve the issue. And yes my SSH
> sessions while Git is "broken" continue to work like a champ, so it's not SSH.
> I've attached cygcheck. Before I even posted I went looking for strace() to
> no avail. I also even did a manual connection attempt like this:   

>>> ssh blah | git index-pack --stdin -v --fix-thin '--keep=fetch-pack 1011 on SOHO-GP4D633' --pack_header=2,1635

> and it would fail in the same manner as when it had been invoked "normally".

1. Try rebasing your Cygwin install.
2. See if your antivirus is interfering.


--
With best regards,
Andrey Repin
Saturday, January 9, 2021 5:22:54

Sorry for my terrible english...
--
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple

[Cygwin list mailing list]

Andrey wrote:> 1. Try rebasing your Cygwin install.
deleted cygwin64 and installed to \cygwin. Immediate failure. No apparent grace period like before.
> 2. See if your antivirus is interfering.
Had corporate IT put me in a special exclusion group (supposedly) to no avail. See #1

    On Friday, January 8, 2021, 09:35:03 PM EST, Andrey Repin <[hidden email]> wrote:  
 
 Greetings, matthew patton!

> Adam Dinwoodie wrote:
>> This looks like some sort of problem writing to disk to me.  Where are
>> you storing your Git repositories?  Is it on a regular NTFS disk

> plain NTFS (win10 exterprise) with hundreds of GB free. I blew away
> contents of /tmp just to make sure it wasn't something silly going on there.
> It's git pack/unpack aborting the read/write from the pipe which causes SSH
> to then close and tear down the connection. SSH client helpfully provides
> stats on how many packets transferred up/down.

> Achim Gratz wrote:
>> That seems to indicate some sort of behavioral based firewalling or IDS

> I thought it could be that too. Tried with and without corporate VPN. But
> it's worked for over a year with this config and nary a hiccup. And anyway
> if I immediately switch to my WSL (Ubuntu) window or Git-Bash and issue the
> Git commands they run perfectly. Yes my Cygwin and WSL and Git-Bash share
> the exact same repository directories.
> If I blow away the entire Cygwin installation (c:\cygwin64) and re-install
> Cygwin Git it will resume working and do so for a while. Like I mentioned
> previously re-installing Git does not solve the issue. And yes my SSH
> sessions while Git is "broken" continue to work like a champ, so it's not SSH.
> I've attached cygcheck. Before I even posted I went looking for strace() to
> no avail. I also even did a manual connection attempt like this:   

>>> ssh blah | git index-pack --stdin -v --fix-thin '--keep=fetch-pack 1011 on SOHO-GP4D633' --pack_header=2,1635

> and it would fail in the same manner as when it had been invoked "normally".

1. Try rebasing your Cygwin install.
2. See if your antivirus is interfering.


--
With best regards,
Andrey Repin
Saturday, January 9, 2021 5:22:54

Sorry for my terrible english...  
--
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple

[Cygwin list mailing list]

ok, so can someone do the following on their installation? I've narrowed it down to the invocation of git-core/git.exe or any of the other git-core/git* binaries. I get a Windows dialog box no less, with "The application was unable to start correctly".
100(1) $ strace /usr/libexec/git-core/git.exe--- Process 14916 created--- Process 14916 loaded C:\Windows\System32\ntdll.dll at 00007ffda07c0000--- Process 14916 loaded C:\Windows\System32\kernel32.dll at 00007ffd9e870000--- Process 14916 loaded C:\Windows\System32\KernelBase.dll at 00007ffd9dbf0000--- Process 14916 thread 14476 created--- Process 14916 thread 16872 created--- Process 14916 thread 10260 created--- Process 14916 thread 12992 exited with status 0xc0000279--- Process 14916 thread 10260 exited with status 0xc0000279--- Process 14916 thread 16872 exited with status 0xc0000279--- Process 14916 exited with status 0xc0000279
LDD for Cygwin git102(1) $ ldd /usr/libexec/git-core/git.exe        ntdll.dll => /cygdrive/c/WINDOWS/SYSTEM32/ntdll.dll (0x7ffda07c0000)        KERNEL32.DLL => /cygdrive/c/WINDOWS/System32/KERNEL32.DLL (0x7ffd9e870000)        KERNELBASE.dll => /cygdrive/c/WINDOWS/System32/KERNELBASE.dll (0x7ffd9dbf0000)



The same thing in Git-Bash results in:--- Process 17124 created--- Process 17124 loaded C:\Windows\System32\ntdll.dll at 00007ffda07c0000--- Process 17124 loaded C:\Windows\System32\kernel32.dll at 00007ffd9e870000--- Process 17124 loaded C:\Windows\System32\KernelBase.dll at 00007ffd9dbf0000--- Process 17124 thread 15280 created--- Process 17124 thread 18192 created--- Process 17124 loaded C:\Windows\System32\advapi32.dll at 00007ffda0070000--- Process 17124 thread 8520 created--- Process 17124 loaded C:\Windows\System32\msvcrt.dll at 00007ffd9eb40000--- Process 17124 loaded C:\Windows\System32\sechost.dll at 00007ffd9e9e0000--- Process 17124 loaded C:\Program Files\Git\mingw64\bin\libiconv-2.dll at 00007ffd68d80000--- Process 17124 loaded C:\Program Files\Git\mingw64\bin\libpcre2-8-0.dll at 0000000064380000--- Process 17124 loaded C:\Windows\System32\rpcrt4.dll at 00007ffd9f4e0000--- Process 17124 loaded C:\Program Files\Git\mingw64\bin\libintl-8.dll at 00007ffd89600000--- Process 17124 loaded C:\Program Files\Git\mingw64\bin\zlib1.dll at 00007ffd895d0000--- Process 17124 loaded C:\Windows\System32\user32.dll at 00007ffd9fe50000--- Process 17124 loaded C:\Windows\System32\win32u.dll at 00007ffd9dbc0000--- Process 17124 loaded C:\Windows\System32\gdi32.dll at 00007ffda04c0000--- Process 17124 loaded C:\Windows\System32\gdi32full.dll at 00007ffd9e630000--- Process 17124 loaded C:\Windows\System32\msvcp_win.dll at 00007ffd9e7d0000--- Process 17124 loaded C:\Windows\System32\ucrtbase.dll at 00007ffd9d730000--- Process 17124 loaded C:\Windows\System32\ws2_32.dll at 00007ffd9fde0000--- Process 17124 loaded C:\Program Files\Git\mingw64\bin\libssp-0.dll at 00007ffd8d120000--- Process 17124 loaded C:\Windows\System32\imm32.dll at 00007ffd9f600000--- Process 17124 loaded C:\Windows\System32\cryptsp.dll at 00007ffd9d8c0000--- Process 17124 loaded C:\Windows\System32\rsaenh.dll at 00007ffd9c710000--- Process 17124 loaded C:\Windows\System32\bcrypt.dll at 00007ffd9d8e0000--- Process 17124 loaded C:\Windows\System32\cryptbase.dll at 00007ffd9cf80000--- Process 17124 loaded C:\Windows\System32\bcryptprimitives.dll at 00007ffd9d830000--- Process 17124 thread 18192 exited with status 0x1--- Process 17124 thread 8520 exited with status 0x1--- Process 17124 thread 15280 exited with status 0x1--- Process 17124 exited with status 0x1
LDD for Git-Bash76(1) $ ldd /mingw64/libexec/git-core/git.exe        ntdll.dll => /c/WINDOWS/SYSTEM32/ntdll.dll (0x7ffda07c0000)        KERNEL32.DLL => /c/WINDOWS/System32/KERNEL32.DLL (0x7ffd9e870000)        KERNELBASE.dll => /c/WINDOWS/System32/KERNELBASE.dll (0x7ffd9dbf0000)        ADVAPI32.dll => /c/WINDOWS/System32/ADVAPI32.dll (0x7ffda0070000)        msvcrt.dll => /c/WINDOWS/System32/msvcrt.dll (0x7ffd9eb40000)        libpcre2-8-0.dll => /mingw64/libexec/git-core/libpcre2-8-0.dll (0x64380000)        libintl-8.dll => /mingw64/libexec/git-core/libintl-8.dll (0x7ffd9bd80000)        sechost.dll => /c/WINDOWS/System32/sechost.dll (0x7ffd9e9e0000)        libiconv-2.dll => /mingw64/libexec/git-core/libiconv-2.dll (0x7ffd66600000)        RPCRT4.dll => /c/WINDOWS/System32/RPCRT4.dll (0x7ffd9f4e0000)        zlib1.dll => /mingw64/libexec/git-core/zlib1.dll (0x7ffd69610000)        USER32.dll => /c/WINDOWS/System32/USER32.dll (0x7ffd9fe50000)        win32u.dll => /c/WINDOWS/System32/win32u.dll (0x7ffd9dbc0000)        GDI32.dll => /c/WINDOWS/System32/GDI32.dll (0x7ffda04c0000)        gdi32full.dll => /c/WINDOWS/System32/gdi32full.dll (0x7ffd9e630000)        msvcp_win.dll => /c/WINDOWS/System32/msvcp_win.dll (0x7ffd9e7d0000)        ucrtbase.dll => /c/WINDOWS/System32/ucrtbase.dll (0x7ffd9d730000)        WS2_32.dll => /c/WINDOWS/System32/WS2_32.dll (0x7ffd9fde0000)        libssp-0.dll => /mingw64/libexec/git-core/libssp-0.dll (0x7ffd9ad00000)
--
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple

[Cygwin list mailing list]

ring a bell with anyone?
C:\Users\mp1116\Downloads>Err_6.4.5.exe 0xc0000279# for hex 0xc0000279 / decimal -1073741191  STATUS_IO_REPARSE_TAG_NOT_HANDLED                              ntstatus.h# The layered file system driver for this IO tag did not# handle it when needed.# as an HRESULT: Severity: FAILURE (1), FACILITY_NULL (0x0), Code 0x279# for hex 0x279 / decimal 633

--
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple

[Brian Inglis]

Could you please figure out how to send your logs as utf8 plain text attachments
or otherwise send as verbatim utf8 plain text with line breaks, as your logs
come across mainly as wrapped single lines in a base64 encoded blob, which few
will bother to try reading.

On 2021-01-14 12:20, matthew patton via Cygwin wrote:
> ok, so can someone do the following on their installation? I've narrowed it down to the invocation of git-core/git.exe or any of the other git-core/git* binaries. I get a Windows dialog box no less, with "The application was unable to start correctly".
> 100(1) $ strace /usr/libexec/git-core/git.exe--- Process 14916 created--- Process 14916 loaded C:\Windows\System32\ntdll.dll at 00007ffda07c0000--- Process 14916 loaded C:\Windows\System32\kernel32.dll at 00007ffd9e870000--- Process 14916 loaded C:\Windows\System32\KernelBase.dll at 00007ffd9dbf0000--- Process 14916 thread 14476 created--- Process 14916 thread 16872 created--- Process 14916 thread 10260 created--- Process 14916 thread 12992 exited with status 0xc0000279--- Process 14916 thread 10260 exited with status 0xc0000279--- Process 14916 thread 16872 exited with status 0xc0000279--- Process 14916 exited with status 0xc0000279
> LDD for Cygwin git102(1) $ ldd /usr/libexec/git-core/git.exe        ntdll.dll => /cygdrive/c/WINDOWS/SYSTEM32/ntdll.dll (0x7ffda07c0000)        KERNEL32.DLL => /cygdrive/c/WINDOWS/System32/KERNEL32.DLL (0x7ffd9e870000)        KERNELBASE.dll => /cygdrive/c/WINDOWS/System32/KERNELBASE.dll (0x7ffd9dbf0000)
>
>
>
> The same thing in Git-Bash results in:--- Process 17124 created--- Process 17124 loaded C:\Windows\System32\ntdll.dll at 00007ffda07c0000--- Process 17124 loaded C:\Windows\System32\kernel32.dll at 00007ffd9e870000--- Process 17124 loaded C:\Windows\System32\KernelBase.dll at 00007ffd9dbf0000--- Process 17124 thread 15280 created--- Process 17124 thread 18192 created--- Process 17124 loaded C:\Windows\System32\advapi32.dll at 00007ffda0070000--- Process 17124 thread 8520 created--- Process 17124 loaded C:\Windows\System32\msvcrt.dll at 00007ffd9eb40000--- Process 17124 loaded C:\Windows\System32\sechost.dll at 00007ffd9e9e0000--- Process 17124 loaded C:\Program Files\Git\mingw64\bin\libiconv-2.dll at 00007ffd68d80000--- Process 17124 loaded C:\Program Files\Git\mingw64\bin\libpcre2-8-0.dll at 0000000064380000--- Process 17124 loaded C:\Windows\System32\rpcrt4.dll at 00007ffd9f4e0000--- Process 17124 loaded C:\Program Files\Git\mingw64\bin\libintl-8.dll at 00007ffd89600000--- Process 17124 loaded C:\Program Files\Git\mingw64\bin\zlib1.dll at 00007ffd895d0000--- Process 17124 loaded C:\Windows\System32\user32.dll at 00007ffd9fe50000--- Process 17124 loaded C:\Windows\System32\win32u.dll at 00007ffd9dbc0000--- Process 17124 loaded C:\Windows\System32\gdi32.dll at 00007ffda04c0000--- Process 17124 loaded C:\Windows\System32\gdi32full.dll at 00007ffd9e630000--- Process 17124 loaded C:\Windows\System32\msvcp_win.dll at 00007ffd9e7d0000--- Process 17124 loaded C:\Windows\System32\ucrtbase.dll at 00007ffd9d730000--- Process 17124 loaded C:\Windows\System32\ws2_32.dll at 00007ffd9fde0000--- Process 17124 loaded C:\Program Files\Git\mingw64\bin\libssp-0.dll at 00007ffd8d120000--- Process 17124 loaded C:\Windows\System32\imm32.dll at 00007ffd9f600000--- Process 17124 loaded C:\Windows\System32\cryptsp.dll at 00007ffd9d8c0000--- Process 17124 loaded C:\Windows\System32\rsaenh.dll at 00007ffd9c710000--- Process 17124 loaded C:\Windows\System32\bcrypt.dll at 00007ffd9d8e0000--- Process 17124 loaded C:\Windows\System32\cryptbase.dll at 00007ffd9cf80000--- Process 17124 loaded C:\Windows\System32\bcryptprimitives.dll at 00007ffd9d830000--- Process 17124 thread 18192 exited with status 0x1--- Process 17124 thread 8520 exited with status 0x1--- Process 17124 thread 15280 exited with status 0x1--- Process 17124 exited with status 0x1
> LDD for Git-Bash76(1) $ ldd /mingw64/libexec/git-core/git.exe        ntdll.dll => /c/WINDOWS/SYSTEM32/ntdll.dll (0x7ffda07c0000)        KERNEL32.DLL => /c/WINDOWS/System32/KERNEL32.DLL (0x7ffd9e870000)        KERNELBASE.dll => /c/WINDOWS/System32/KERNELBASE.dll (0x7ffd9dbf0000)        ADVAPI32.dll => /c/WINDOWS/System32/ADVAPI32.dll (0x7ffda0070000)        msvcrt.dll => /c/WINDOWS/System32/msvcrt.dll (0x7ffd9eb40000)        libpcre2-8-0.dll => /mingw64/libexec/git-core/libpcre2-8-0.dll (0x64380000)        libintl-8.dll => /mingw64/libexec/git-core/libintl-8.dll (0x7ffd9bd80000)        sechost.dll => /c/WINDOWS/System32/sechost.dll (0x7ffd9e9e0000)        libiconv-2.dll => /mingw64/libexec/git-core/libiconv-2.dll (0x7ffd66600000)        RPCRT4.dll => /c/WINDOWS/System32/RPCRT4.dll (0x7ffd9f4e0000)        zlib1.dll => /mingw64/libexec/git-core/zlib1.dll (0x7ffd69610000)        USER32.dll => /c/WINDOWS/System32/USER32.dll (0x7ffd9fe50000)        win32u.dll => /c/WINDOWS/System32/win32u.dll (0x7ffd9dbc0000)        GDI32.dll => /c/WINDOWS/System32/GDI32.dll (0x7ffda04c0000)        gdi32full.dll => /c/WINDOWS/System32/gdi32full.dll (0x7ffd9e630000)        msvcp_win.dll => /c/WINDOWS/System32/msvcp_win.dll (0x7ffd9e7d0000)        ucrtbase.dll => /c/WINDOWS/System32/ucrtbase.dll (0x7ffd9d730000)        WS2_32.dll => /c/WINDOWS/System32/WS2_32.dll (0x7ffd9fde0000)        libssp-0.dll => /mingw64/libexec/git-core/libssp-0.dll (0x7ffd9ad00000)

--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]
--
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple

[Cygwin list mailing list]

On 1/14/2021 5:27 PM, matthew patton via Cygwin wrote:
> ring a bell with anyone?
> C:\Users\mp1116\Downloads>Err_6.4.5.exe 0xc0000279# for hex 0xc0000279 / decimal -1073741191  STATUS_IO_REPARSE_TAG_NOT_HANDLED                              ntstatus.h# The layered file system driver for this IO tag did not# handle it when needed.# as an HRESULT: Severity: FAILURE (1), FACILITY_NULL (0x0), Code 0x279# for hex 0x279 / decimal 633

Do you by any chance have symlinks in your PATH?  There was a problem reported
in early December in which STATUS_IO_REPARSE_TAG_NOT_HANDLED would sometimes
occur when there was a symlink in PATH:

   https://cygwin.com/pipermail/cygwin/2020-December/246938.html

This was fixed.  You can test whether the same fix works for you by installing
the latest snapshot from

   https://cygwin.com/snapshots/

Ken
--
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple

[Cygwin list mailing list]

Ken Brown wrote:> Do you by any chance have symlinks in your PATH?
Yes, the first and 3rd entries are symlinks. I've had these symlinks in my PATH for years.
/home/MP1116/.aws/YYY/bin:/home/MP1116/bin -> .WPHOME/bin/

.aws -> .WPHOME/.aws/.WPHOME -> Dropbox/Work_Projects/XXX
#/etc/fstabC:/Users /home none binary,user 0 0

>  There was a problem reported in early December in which STATUS_IO_REPARSE_TAG_NOT_HANDLED > would sometimes occur when there was a symlink in PATH:

This KB was released 8 December. I installed it on Dec 23 and my git failures started after that date.https://support.microsoft.com/en-us/help/4592449/windows-10-update-kb4592449


 
--
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple

[Brian Inglis]

On 2021-01-15 09:36, matthew patton via Cygwin wrote:
> Ken Brown wrote:> Do you by any chance have symlinks in your PATH?
> Yes, the first and 3rd entries are symlinks.
> I've had these symlinks in my PATH for years.
> /home/MP1116/.aws/YYY/bin:/home/MP1116/bin -> .WPHOME/bin/
>
> .aws -> .WPHOME/.aws/.WPHOME -> Dropbox/Work_Projects/XXX
> #/etc/fstabC:/Users /home none binary,user 0 0
>
>>    There was a problem reported in early December in which STATUS_IO_REPARSE_TAG_NOT_HANDLED > would sometimes occur when there was a symlink in PATH:

Given that you have the same symptom, it is possible that Git-Bash or something
else you are running in Windows is creating symlinks somewhere, which Cygwin is
attempting to read while resolving some path search, or opening some directory
or file entry, so it would seem advisable to download and install the latest
snapshot DLL.
You could test this by trying to operate with only minimal Cygwin path /usr/bin:
/bin and git clone into Cygwin /tmp/ or /usr/tmp/ as long as they are not
mounted on non-Cygwin directories like your /home is, where Windows programs are
likely to have an impact.

> This KB was released 8 December. I installed it on Dec 23 and my git failures
> started after that date.
> <https://support.microsoft.com/en-us/help/4592449/windows-10-update-kb4592449>
Known issue with that update is loss of user and system certs - hopefully only
from Windows cert store affecting only Windows apps - but could that impact
anything you are using?

--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]
--
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple

[Cygwin list mailing list]

On Friday, January 15, 2021, 12:09:30 PM EST, Brian Inglis <[hidden email]> wrote:
 
 > Given that you have the same symptom, it is possible that Git-Bash or something > else you are running in Windows is creating symlinks somewhere, 
I only installed Git-Bash out of desperation and it's msys.dll (fork of cygwin.dll) is v 3.1.7 and dated late December after Cygwin team published this patch. https://sourceware.org/git/?p=newlib-cygwin.git;a=commit;h=aec6479820fee5f71d50930bf0dde2bbf386bd4b
 
--
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple