From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32299 invoked by alias); 13 Oct 2012 18:21:19 -0000 Received: (qmail 32185 invoked by uid 22791); 13 Oct 2012 18:21:17 -0000 X-SWARE-Spam-Status: No, hits=-5.7 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,KHOP_RCVD_TRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE,TW_CG X-Spam-Check-By: sourceware.org Received: from mail-ee0-f43.google.com (HELO mail-ee0-f43.google.com) (74.125.83.43) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sat, 13 Oct 2012 18:21:13 +0000 Received: by mail-ee0-f43.google.com with SMTP id c13so2304914eek.2 for ; Sat, 13 Oct 2012 11:21:12 -0700 (PDT) Received: by 10.14.220.71 with SMTP id n47mr10578065eep.26.1350152472182; Sat, 13 Oct 2012 11:21:12 -0700 (PDT) Received: from [192.168.2.195] (93-33-103-172.ip44.fastwebnet.it. [93.33.103.172]) by mx.google.com with ESMTPS id i41sm17132055eem.7.2012.10.13.11.21.11 (version=SSLv3 cipher=OTHER); Sat, 13 Oct 2012 11:21:11 -0700 (PDT) Message-ID: <5079B10D.1030108@gmail.com> Date: Sat, 13 Oct 2012 18:21:00 -0000 From: marco atzeri User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121010 Thunderbird/16.0.1 MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: sshd fork failure References: <503F9877.5070406@gmail.com> <20121013153936.GB839@ednor.casa.cgf.cx> <5079926F.1020503@gmail.com> <20121013165405.GC9226@ednor.casa.cgf.cx> In-Reply-To: <20121013165405.GC9226@ednor.casa.cgf.cx> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com X-SW-Source: 2012-10/txt/msg00181.txt.bz2 On 10/13/2012 6:54 PM, Christopher Faylor wrote: > On Sat, Oct 13, 2012 at 06:10:23PM +0200, marco atzeri wrote: >> On 10/13/2012 5:39 PM, Christopher Faylor wrote: >>> 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. >> >> on 20121012 similar but in another location. >> >> --- Process 6280, exception C0000005 at 61137DC8 >> 427 147466 [main] sshd 6280 exception::handle: In >> cygwin_except_handler exception 0xC0000005 at 0x61137DC8 sp 0x289270 >> 67 147533 [main] sshd 6280 exception::handle: In >> cygwin_except_handler signal 11 at 0x61137DC8 >> 38 147571 [main] sshd 6280 exception::handle: In >> cygwin_except_handler calling 0x0 >> 37 147608 [main] sshd 6280 exception::handle: Exception: >> STATUS_ACCESS_VIOLATION >> >> addr2line.exe 61137DC8 -e /usr/bin/cygwin1.dll >> /netrel/src/cygwin-snapshot-20121012-1/newlib/libc/stdio/findfp.c:296 > > You seem to be the only person reporting this problem. Everyone else > updates to a snapshot to cure ssh problems. FWIW, that instruction > shouldn't even be executed. > > cgf > I have such issue only on sshd forking and for long time, so it is not relative to last snapshots. As this the is only program that involve several USER accounts I suspect some crippling "corporate" group policy or a very strange BLODA effect. 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