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]

RE: sshd connections unexpectedly close on windows 2012


> -----Original Message-----
> Sent: Monday, June 18, 2012 16:34
> Subject: Re: sshd connections unexpectedly close on windows 2012
> 
> > "      5 [main] sshd 180 fhandler_dev_zero::fixup_mmap_after_fork:
> requested 0xFEF20000 != 0x0 mem alloc base 0x0, state 0x10000, size
> 1179648, Win32 error 487
> >    2833 [main] sshd 180 C:\cygwin\usr\sbin\sshd.exe: *** fatal error in
> forked process - recreate_mmaps_after_fork_failed
> >    4115 [main] sshd 180 open_stackdumpfile: Dumping stack trace to
> sshd.exe.stackdump
> >       2 [main] sshd 2396 fork: child -1 - forked process 180 died unexpectedly,
> retry 0, exit code 256, errno 11"
> 
> This is probably the same problem as reported in the thread starting at
> 
>   http://cygwin.com/ml/cygwin/2012-06/msg00089.html
> 
> There's no solution yet, sorry.

Just wanting to report that I'm seeing a very similar error on Windows 8 consumer preview with Cygwin snapshot from June 4, 2012.  Yes, I realize that it isn't the latest snapshot - I'll see if I can test on something newer - for now this is just another data point for you.

3 [main] bash 3308 fhandler_dev_zero::fixup_mmap_after_fork: requested 0x7F510000 != 0x0 mem alloc base 0x7F510000, state 0x1000, size 143360, Win32 error 487
1990      268 [main] bash 3308 C:\cygwin\bin\bash.exe: *** fatal error in forked process - recreate_mmaps_after_fork_failed
1991      644 [main] bash 3308 open_stackdumpfile: Dumping stack trace to bash.exe.stackdump
1992        4 [main] TestScript 3744 fork: child -1 - forked process 3308 died unexpectedly, retry 0, exit code 256, errno 11

This was reproduced three times, and each had an error very similar to this one.  At the time of the crash, a bash script was running which was probably invoking either another subshell or perl.  Note that all DLLs had been rebased to not conflict with each other or with ASLR-relocated system DLLs.

This error seems to be very similar to the errors recently reported by Bertrand Latinville and Arnon Yaari:
* Win32 error is the same (487).
* The same functions crashed: fixup_mmap_after_fork, recreate_mmaps_after_fork_failed
* In general, the error looks about the same.

Given that the problem hasn't been fixed and it seems to be most likely to be the same problem as the others, I doubt that upgrading to a newer Windows 8 and Cygwin will help.


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