This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Cygwin 3.1.X Fatal Errors - add_item ("\??\C:", "/", ...) failed, errno 22


This is related to https://cygwin.com/ml/cygwin/2020-01/msg00045.html. I
have now tried the same update on two other systems.

Cygwin 3.0.7-1 32-bit works fine on three different systems: one Windows 7
64-bit, two Windows 10 64-bit. However, Cygwin 3.1.1-1 and 3.2.1-1 fail to
install cleanly on these systems and leave me with a Cygwin installation
that gives fatal errors.

In response to Marco Atzeri's comments:

| testing on my W10 64bit a clean 32bit installation from scratch
| I seen no issues

The problem may be due to an update from a previous version of Cygwin rather
than a clean install. I haven't yet tried completely uninstalling and
reinstalling Cygwin on these systems, but will do so if necessary.

| for what I know exit code=-1073741819 is in
| HEX FFFF FFFF C000 0005
|
| and Exception code c0000005 is the code for an access violation

That's correct. It's something deep within Cygwin that's failing. After
trying to install Cygwin 3.1.1-1 or 3.2.1-1, I rebooted to make sure that
the new cygwin1 DLL was being used. All Cygwin binaries (dash, ls, rebase,
etc.) then fail with:

*** fatal error - add_item ("\??\C:", "/", ...) failed, errno 22

This may be due to a forking issue rather than a rebase issue. On tracing
"ls" there is a strange reference to '\??\C'. Could that be related to a
cygdrive prefix problem or a mount problem?

strace ls

--- Process 13624 created
--- Process 13624 loaded C:\Windows\SysWOW64\ntdll.dll at 77dc0000
--- Process 13624 loaded C:\Windows\SysWOW64\kernel32.dll at 77290000
--- Process 13624 loaded C:\Windows\SysWOW64\KernelBase.dll at 77090000
--- Process 13624 thread 16620 created
--- Process 13624 thread 15828 created
--- Process 13624 thread 15592 created
--- Process 13624 loaded C:\bin\cygwin1.dll at 61000000
--- Process 13624 loaded C:\bin\cygintl-8.dll at 6e700000
--- Process 13624 loaded C:\bin\cyggcc_s-1.dll at 6f120000
--- Process 13624 loaded C:\bin\cygiconv-2.dll at 6e770000
    0       0 [main] ls (13624)
**********************************************
  187     187 [main] ls (13624) Program name: C:\bin\ls.exe (windows pid
13624)
  124     311 [main] ls (13624) OS version:   Windows NT-10.0
  119     430 [main] ls (13624)
**********************************************
...
  104    9118 [main] ls (13624) fhandler_pipe::create: name
\\.\pipe\cygwin-a46ac466ed629d62-13624-sigwait, size 5412, mode
PIPE_TYPE_MESSAGE
  148    9266 [main] ls (13624) fhandler_pipe::create: pipe read handle
0x158
   83    9349 [main] ls (13624) fhandler_pipe::create: CreateFile: name
\\.\pipe\cygwin-a46ac466ed629d62-13624-sigwait
  135    9484 [main] ls (13624) fhandler_pipe::create: pipe write handle
0x15C
   87    9571 [main] ls (13624) dll_crt0_0: finished dll_crt0_0
initialization
  193    9764 [main] ls (13624) dll_list::ntopenfile: 0xC0000034 =
NtOpenFile (0x0, a 100081h, sh 7h, o 21h, io 0x18008, :\var\run\cygfork')
   88    9852 [main] ls (13624) dll_list::forkable_ntnamesize: disabled,
missing or not on NTFS \??\C:\var\run\cygfork
--- Process 13624 thread 13764 created
  701   10553 [main] ls (13624) time: 1578834212 = time(0x0)
  139   10692 [main] ls (13624) normalize_posix_path: src /
   52   10744 [main] ls (13624) normalize_posix_path: / =
normalize_posix_path (/)
   52   10796 [main] ls (13624) mount_info::add_item: \??\C:[error], /[/],
0x30008
  161   10957 [sig] ls (13624) wait_sig: entering ReadFile loop, my_readsig
0x158, my_sendsig 0x15C
   65   11022 [main] ls (13624) __set_errno: int mount_info::add_item(const
char*, const char*, unsigned int):1400 setting errno 22
  11117 [main] ls (13624) C:\bin\ls.exe: *** fatal error - add_item
("\??\C:", "/", ...) failed, errno 22
   95   11117 [main] ls (13624) C:\bin\ls.exe: *** fatal error - add_item
("\??\C:", "/", ...) failed, errno 22

Stack trace:
Frame     Function  Args
--- Process 13624, exception c0000005 at 610210ff
 1360   12477 [main] ls (13624) proc_terminate: nprocs 0
  156   12633 [main] ls (13624) proc_terminate: leaving
  171   12804 [main] ls (13624) pinfo::exit: Calling dlls.cleanup_forkables
n 0x1, exitcode 0x100
  172   12976 [main] ls (13624) pinfo::exit: Calling ExitProcess n 0x1,
exitcode 0x100
--- Process 13624 thread 15136 exited with status 0x100
--- Process 13624 thread 15828 exited with status 0x100
--- Process 13624 thread 16620 exited with status 0x100
--- Process 13624 thread 15592 exited with status 0x100
--- Process 13624 exited with status 0x100

| some BLODA around ?

Checking the list at https://cygwin.com/faq/faq.html#faq.using.bloda, I
don't believe I have any of the possibly problematic apps mentioned.

I wonder why Cygwin 3.0.7-1 would work fine but not any later version.
Evidently there is a significant difference in later versions.

I see the same errors when trying to update three different systems (one
Windows 7, two Windows 10), so it isn't specific to one system. These also
have different mounts for different disks (respectively C: is an HDD, C: is
an SSD, C: is an SSD and D: is an HDD).

What is common to these systems is that they are 64-bit Windows being used
with 32-bit Cygwin, that Cygwin is installed in the root of the C drive, and
that I'm trying to update from Cygwin 3.0.7-1 rather than doing a clean
install.


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]