On Thu, Aug 30, 2012 at 06:44:39PM +0200, marco atzeri wrote: >Hi, >tracing the sshd process on latest cygwin shapshot , >I see that the fork is failing due to exception C0000005 > > 1 1 [main] sshd (4644) >********************************************** > 5921 5922 [main] sshd (4644) Program name: >E:\cygwin\usr\sbin\sshd.exe (windows pid 4644) > 30 5952 [main] sshd (4644) OS version: Windows NT-6.1 > 25 5977 [main] sshd (4644) >********************************************** > 636 6613 [main] sshd (4644) sigprocmask: 0 = sigprocmask (0, >0x6123D428, 0x610FBB30) > 122 6735 [main] sshd 4644 child_copy: cygheap - hp 0x20C low >0x612708D0, high 0x61277640, res 1 > 1368 8103 [main] sshd 4644 child_copy: done >--- Process 4644, exception C0000005 at 61137277 > > > >$ addr2line.exe 61137277 -e /usr/bin/cygwin1.dll >/netrel/src/cygwin-snapshot-20120827-1/newlib/libc/stdlib/mbtowc_r.c:323 > >that should be: > > ch = (state->__count == 1) ? t[i++] : state->__value.__wchb[1]; > >inside __utf8_mbtowc . >It looks a strange place for a fork failure, but it is used in >winsup/cygwin/cygheap.cc so it could make sense. > >Any suggestion how to follow/debug the child portion of fork ?
Is this still failing? We're looking to release 1.7.17 soon. cgf -- 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