On Apr 20 16:58, Bruno Haible via Cygwin wrote: > Corinna Vinschen wrote: > > > Hmm. Your code uses lpReserved2 for that, but the functionality is > > > one implemented in MSVCRT. For obvious reasons, Cygwin executables > > > are not linked against msvcrt.dll and we're using lpReserved2 for our > > > own purposes. > > > > Oh, btw., did you know that there's a newer mechanism for defining > > specific inheritable handles to CreateProcess, which is implemented > > in kernel32.dll, so it does not depend on MSVCRT? > > > > There's a STARTUPINFOEX structure which allows to specify the > > additional handles. See > > > > https://learn.microsoft.com/en-us/windows/win32/api/winbase/ns-winbase-startupinfoexa > > > > and the PROC_THREAD_ATTRIBUTE_HANDLE_LIST argument described in > > > > https://learn.microsoft.com/en-us/windows/win32/api/processthreadsapi/nf-processthreadsapi-updateprocthreadattribute > > Indeed, this appears to be a more "official" way to pass handles for fd ≥ 3, > instead of lpReserved2 — albeit without associated 'flags'. Not sure how > O_APPEND is handled then...
Yeah, theoretically, that should be handled by CreateFile opening the file with FILE_APPEND_DATA attribute, and in the child MSVCRT should test with NtQueryInformationFile(FILE_ACCESS_INFORMATION) if the FILE_APPEND_DATA flag is set. But then again, if MSVCRT implements fcntl (F_SETFL) to allow manipulating the O_APPEND flag... unfortunately there's no such operation via Win32 or native calls. That would require to reopen the file with different access mask and replace the HANDLE under the hood of the descriptor. I'm not aware if and how MSVCRT performs this action. Corinna -- 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
