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:references:to:reply-to:from:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=BQf36w9IH4QMPzHj
	HMC09rQacu1fK3zYwgP2idobHKhyvHjf+NBxnMt0j5pos2BId0Vd/iJnXATqE10l
	wd7/hD+0aogYA2YJuB9vg2ALa3LkvUTWxABTALq/kEROYEYHdqoYfXeUwOvz82NG
	2bWB0qfqgF6MVVPvqFzTTetmpSM=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Subject: Re: Random "child_info_fork::abort:"
References: <85b945fb-0b5f-e2b3-b899-99176d6e4da2 AT yandex DOT ru>
To: cygwin AT cygwin DOT com
Reply-To: Brian DOT Inglis AT SystematicSw DOT ab DOT ca
From: Brian Inglis <Brian DOT Inglis AT SystematicSw DOT ab DOT ca>
Message-ID: <d879b90e-70b4-2b08-5c5b-3faccd89365b@SystematicSw.ab.ca>
Date: Tue, 11 Oct 2016 23:59:18 -0600
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: <85b945fb-0b5f-e2b3-b899-99176d6e4da2@yandex.ru>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

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?
> Versions:
> $ uname -srvmo
> CYGWIN_NT-10.0 2.6.0(0.304/5/3) 2016-08-31 14:32 x86_64 Cygwin
> $ cat /proc/registry/HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/Windows\
> NT/CurrentVersion/CurrentBuildNumber
> 14931

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?

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

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

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