Custom Query (245 matches)

This happens with the current trunk (064x) under the following conditions:

1. A process using LIBC063.DLL is up and running so that the __LIBC_SPMHEADER structure is already created in the shared memory.

2. A process using LIBC064x.DLL is getting started which results in the above error message.

Debugging LIBC064x.DLL shows that the message appears because the DosOpenEventSem?() here​ returns ERROR_INVALID_HANDLE on a handle which looks OK here (0x800103C or like that).

Note that spmInit() in LIBC063.DLL doesn't do DosOpenEventSem?() (which is not fully clear since this call is kind of required to make use of the semaphore from another process) and therefore if the second process is LIBC063.DLL-based, it starts fine.

Building coreutils fails under gcc 3.3.5ga2, worked in RC1. chmod +x groups-t chmod: fts_read failed: Function not implemented

LIBC PANIC!! _um_free_maybe_lock: Tried to free block twice - block=20035180 lock=0x1 pid=0x17b6 ppid=0x1351 tid=0x0001 slot=0x00c5 pri=0x0200 mc=0x0000 E:\CVS\WORK\COREUTILS-5.2.1\SRC\CHMOD.EXE Process have been dumped

LIBC marks the Extended Attributes used to support unix file attribute emulation as critical (FEA_NEEDEA). This prevents non-EA aware applications from opening these files on HPFS formatted volumes.

The particular use-case was that a user ran some application that applied LIBC EAs to uhpfs.dll. Format.com reported

SYS1311: The system files are missing.

because the DosLoadModule?() libpath search failed to find a uhpfs.dll that could be opened.

Note that this issue does not affect jfs formatted volumes. It appears that jfs.ifs does not check if the application supports EAs.