From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32381 invoked by alias); 13 Oct 2012 21:17:55 -0000 Received: (qmail 32372 invoked by uid 22791); 13 Oct 2012 21:17:54 -0000 X-SWARE-Spam-Status: No, hits=-3.6 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RP_MATCHES_RCVD,SPF_HELO_PASS,TW_CG X-Spam-Check-By: sourceware.org Received: from malth.us (HELO malth.us) (75.147.143.249) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sat, 13 Oct 2012 21:17:51 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by malth.us (Postfix) with ESMTP id B3CC140CA3A7 for ; Sat, 13 Oct 2012 14:17:50 -0700 (PDT) Received: from malth.us ([127.0.0.1]) by localhost (malth.us [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b1KUFlgdtjLg for ; Sat, 13 Oct 2012 14:17:35 -0700 (PDT) Received: from [192.168.0.175] (moneypit.hq [192.168.0.175]) by malth.us (Postfix) with ESMTPSA id 2BBB040CA51E for ; Sat, 13 Oct 2012 14:17:35 -0700 (PDT) Message-ID: <5079DA6F.5080600@malth.us> Date: Sat, 13 Oct 2012 21:17:00 -0000 From: "Gregory M. Turner" User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120907 Thunderbird/15.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> <5079B10D.1030108@gmail.com> <20121013182449.GA10736@ednor.casa.cgf.cx> <5079BF50.1020503@gmail.com> <20121013192612.GB10736@ednor.casa.cgf.cx> <5079D77A.8040908@gmail.com> In-Reply-To: <5079D77A.8040908@gmail.com> 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/msg00186.txt.bz2 On 10/13/2012 2:04 PM, marco atzeri wrote: > On 10/13/2012 9:26 PM, Christopher Faylor wrote: > >> >> No. This has nothing to do with cygwin1.dbg. The address 61137DC8 is >> in the middle of an instruction. >> >> cgf >> > > after a second rebaseall and a full updatedb to look for any > other cygwin1.dll, now sshd is working as expected. > > It does not make sense..... > > waiting to see 1.7.17 Sensibly or not, these base-address issues can be quite intermittent -- remember that cygwin is not the only player in this drama. I have several times seen repeatable cycles of fork failures, where attempt #1 always fails, attempt #2 always succeeds, attempt #3 always fails, and so on. -gmt -- 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