delorie.com/archives/browse.cgi | search |
X-Recipient: | archive-cygwin AT delorie DOT com |
X-SWARE-Spam-Status: | No, hits=-4.9 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,KHOP_RCVD_TRUST,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE |
X-Spam-Check-By: | sourceware.org |
Message-ID: | <503F9877.5070406@gmail.com> |
Date: | Thu, 30 Aug 2012 18:44:39 +0200 |
From: | marco atzeri <marco DOT atzeri AT gmail DOT com> |
User-Agent: | Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0 |
MIME-Version: | 1.0 |
To: | cygwin AT cygwin DOT com |
Subject: | sshd fork failure |
X-IsSubscribed: | yes |
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
List-Id: | <cygwin.cygwin.com> |
List-Subscribe: | <mailto:cygwin-subscribe AT cygwin DOT com> |
List-Archive: | <http://sourceware.org/ml/cygwin/> |
List-Post: | <mailto:cygwin AT cygwin DOT com> |
List-Help: | <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs> |
Sender: | cygwin-owner AT cygwin DOT com |
Mail-Followup-To: | cygwin AT cygwin DOT com |
Delivered-To: | mailing list cygwin AT cygwin DOT com |
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 ? Marco -- 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
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |