X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=JgQYiNIb8uBjOApT
	3gQ3nFVpqPr0ChytyY1E7lyOp6yusaX5QLb9F4Gi4kt5PYi/ePrsKCo0D6JUgfgq
	FedBD1n3AA85nA2k4L2jRC6pkXlPUNGwsaHPItj/qj/7Vwce7Unpd/gEFW0tclpZ
	hlGB5xszIULr9m1x6y/ohZFWWcM=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=TssclHiyzIkRut3TPiLeUN
	7EUVs=; b=Ujjjw1E4k8jjBgIq/4oRwW/lG2c+xkMLWVhlZ6OUVsyBDtbubTdOqi
	l7YfPhZMeNlLeJUaXlD9BNs8LXxM8gYHFfC4obF8suHIx19I2LA5e8RHfDGwcWWI
	Udrzvr1BkWKDvVwHiZqqUTPzuzr/b4NKuwmBRfSCgLrLvypNt3g9w=
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
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-2.6 required=5.0 tests=BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy=H*i:sk:d879b90, H*f:sk:d879b90, H*MI:sk:d879b90, UD:ru
X-HELO: forward5h.cmail.yandex.net
Authentication-Results: smtp3p.mail.yandex.net; dkim=pass header.i=@yandex.ru
X-Yandex-Suid-Status: 1 0
Subject: Re: Random "child_info_fork::abort:"
To: cygwin AT cygwin DOT com
References: <85b945fb-0b5f-e2b3-b899-99176d6e4da2 AT yandex DOT ru> <d879b90e-70b4-2b08-5c5b-3faccd89365b AT SystematicSw DOT ab DOT ca>
From: Evgeny Grin <k2k AT yandex DOT ru>
Openpgp: id=289FE99E138CF6D473A3F0CFBF7AC4A5EAC2BAF4
Message-ID: <d4735765-890e-a34b-93ee-d17b9c102a9d@yandex.ru>
Date: Wed, 12 Oct 2016 13:59:17 +0300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <d879b90e-70b4-2b08-5c5b-3faccd89365b@SystematicSw.ab.ca>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

On 12.10.2016 8:59, Brian Inglis wrote:
> On 2016-10-11 15:32, Evgeny Grin wrote:
>> I'm using Windows Insider (slow ring, prerelease). After recent update
>> to build 14931, cygwin keeps randomly fail on fork. This happens not
>> every fork, but frequent enough. Simplest way to trigger it is to run
>> mandb.
>> At variable delay I got something like
>> child_info_fork::abort: T:\cygwin64\bin\cygman-2-7-5.dll: Loaded to
>> different address: parent(0x3FEAB0000) != child(0x1C0000)
>> Dll name and child address may vary.
>> I updated cygwin to latest version, but problem remains.
>> Exactly the same problem with Msys2, but additionally from time to time
>> I got different error:
>> *** fatal error - cygheap base mismatch detected - 0x1802FE408/0x106E408.
>> This problem is probably due to....
> 
>> I set variable CYGWIN=detect_bloda, but nothing is detected.
>> What else could I check?
> 
> Run rebase -is to check for DLL conflicts.
> After the update did you run "rebase-trigger full" and setup,
> with NO Cygwin processes running, to remap the system DLLs
> and rebase the Cygwin DLLs?

Done. No conflicts.
Setup run fine, problem is not solved.

Observation: Cygwin errors appears more often than Msys2 errors.
Even got initial loading on incorrect address:

child_info_fork::abort: T:\cygwin64\bin\cygman-2-7-5.dll: Loaded to
different address: parent(0x190000) != child(0x3FB700000)

> It's likely the Insider debug builds dynamically enable/disable
> features and functions or run alternate system DLLs which gather
> info by acting as BLODAs.
> MS can mess around with your systems to enable new stuff (possibly
> in different combinations) and see which systems they cause problems
> on.
> Hopefully they can also dynamically revert new releases causing
> problems.
> Your systems are the canaries for their Continuous Delivery QA.
> 
> Make sure you continously back up any work on those systems and
> don't ignore warnings, especially build expiries (you are meant
> to be allowed 3 reboots after expiry before the buildrefuses
> to boot!)

Thanks!
Not sure that situation is just "test" or "temporary". I'm using
prerelease track so this can go to release.

--
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