X-Recipient: archive-cygwin AT delorie DOT com
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
Message-ID: <5079DA6F.5080600@malth.us>
Date: Sat, 13 Oct 2012 14:17:35 -0700
From: "Gregory M. Turner" <gmt AT malth DOT us>
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 AT cygwin DOT com
Subject: Re: sshd fork failure
References: <503F9877 DOT 5070406 AT gmail DOT com> <20121013153936 DOT GB839 AT ednor DOT casa DOT cgf DOT cx> <5079926F DOT 1020503 AT gmail DOT com> <20121013165405 DOT GC9226 AT ednor DOT casa DOT cgf DOT cx> <5079B10D DOT 1030108 AT gmail DOT com> <20121013182449 DOT GA10736 AT ednor DOT casa DOT cgf DOT cx> <5079BF50 DOT 1020503 AT gmail DOT com> <20121013192612 DOT GB10736 AT ednor DOT casa DOT cgf DOT cx> <5079D77A DOT 8040908 AT gmail DOT 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 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

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