Recent snapshots somewhat fail under W7

Recent snapshots somewhat fail under W7

[Denis Excoffier]

Hello,

I tried the (numerous) recent snapshots with W10 (1709) with no problem (except for the isolated 20190115 snapshot and also that « cp cygwin0.dll /usr/bin/cygwin1.dll » now fails but this is another story). The recent snapshots with W7 fail somewhat (but the system seems to function more or less), i've got the following message with W7:

      0 [main] tcsh 15528 fixup_mmaps_after_fork: VirtualQueryEx failed for MAP_PRIVATE address 0x6FFFFFA0000, Win32 error 5
    368 [main] tcsh 15528 D:\Users\dexcoff1\dexcoff1\cyglcl\uxl\tcsh-6.20.00\bin\tcsh.exe: *** fatal error in forked process - recreate_mmaps_after_fork_failed
    700 [main] tcsh 15528 cygwin_exception::open_stackdumpfile: Dumping stack trace to tcsh.exe.stackdump
      0 [main] tcsh 19080 fork: child -1 - forked process 15528 died unexpectedly, retry 0, exit code 0x100, errno 11
No more processes.

I had a look into sigproc.cc <http://sigproc.cc/> and noticed that recently (commit 69cc7a068656b5c6ef07ca079a213f801e02e650, dated 2019-01-27, DUPLICATE_SAME_ACCESS has been replaced by 0 in a call to DuplicateHandle(). I switched it back, re-compiled and the fork problem above disappeared. Don’t know the impact on W10.

HTH.

Denis Excoffier.





--
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

Re: Recent snapshots somewhat fail under W7

[Corinna Vinschen]

[-- Attachment #1: Type: text/plain, Size: 1896 bytes --]

On Jan 29 23:50, Denis Excoffier wrote:
> Hello,
> 
> I tried the (numerous) recent snapshots with W10 (1709) with no
> problem (except for the isolated 20190115 snapshot and also that « cp
> cygwin0.dll /usr/bin/cygwin1.dll » now fails but this is another
> story). The recent snapshots with W7 fail somewhat (but the system
> seems to function more or less), i've got the following message with
> W7:
> 
>       0 [main] tcsh 15528 fixup_mmaps_after_fork: VirtualQueryEx
>       failed for MAP_PRIVATE address 0x6FFFFFA0000, Win32 error 5 368
>       [main] tcsh 15528
>       D:\Users\dexcoff1\dexcoff1\cyglcl\uxl\tcsh-6.20.00\bin\tcsh.exe:
>       *** fatal error in forked process -
>       recreate_mmaps_after_fork_failed 700 [main] tcsh 15528
>       cygwin_exception::open_stackdumpfile: Dumping stack trace to
>       tcsh.exe.stackdump 0 [main] tcsh 19080 fork: child -1 - forked
>       process 15528 died unexpectedly, retry 0, exit code 0x100, errno
>       11 No more processes.
> 
> I had a look into sigproc.cc <http://sigproc.cc/> and noticed that
> recently (commit 69cc7a068656b5c6ef07ca079a213f801e02e650, dated
> 2019-01-27, DUPLICATE_SAME_ACCESS has been replaced by 0 in a call to
> DuplicateHandle(). I switched it back, re-compiled and the fork
> problem above disappeared. Don’t know the impact on W10.
>
> HTH.

Kind of.  This patch is not switch to 0 something, but from automatic
permission inheritence to explicit, minimal permissions required.

I was going to ask for a testcase and more info about your system(*)
but then I was able to reproduce it myself.  It seems W7 needs more
permissions for VirtualQueryEx than Windows 8 and later.  I applied a
patch.  New test release coming soon.


Corinna

(*) It would really be nice not having to ask for these infos every time.

-- 
Corinna Vinschen
Cygwin Maintainer

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]