This is the mail archive of the
mailing list for the Cygwin project.
Re: Random "child_info_fork::abort:"
- From: Brian Inglis <Brian dot Inglis at SystematicSw dot ab dot ca>
- To: cygwin at cygwin dot com
- Date: Tue, 11 Oct 2016 23:59:18 -0600
- Subject: Re: Random "child_info_fork::abort:"
- Authentication-results: sourceware.org; auth=none
- References: <email@example.com>
- Reply-to: Brian dot Inglis at SystematicSw dot ab dot ca
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?
$ 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\
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
Hopefully they can also dynamically revert new releases causing
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
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple