From: Evgeny Grin <k2k@yandex.ru>
To: cygwin@cygwin.com
Subject: Re: Random "child_info_fork::abort:"
Date: Wed, 12 Oct 2016 12:00:00 -0000 [thread overview]
Message-ID: <d4735765-890e-a34b-93ee-d17b9c102a9d@yandex.ru> (raw)
In-Reply-To: <d879b90e-70b4-2b08-5c5b-3faccd89365b@SystematicSw.ab.ca>
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
next prev parent reply other threads:[~2016-10-12 10:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-12 5:59 Evgeny Grin
2016-10-12 8:36 ` Brian Inglis
2016-10-12 12:00 ` Evgeny Grin [this message]
2016-10-13 4:43 ` Evgeny Grin
2016-10-13 12:00 ` Evgeny Grin
2016-10-13 12:31 ` Marco Atzeri
2016-10-13 13:12 ` Eliot Moss
2016-10-13 14:35 ` Brian Inglis
2016-10-13 16:29 ` Evgeny Grin
2016-10-13 17:56 ` Evgeny Grin
2016-10-13 21:05 ` Evgeny Grin
2016-10-15 10:28 ` Tony Kelman
2016-10-16 0:08 ` Evgeny Grin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d4735765-890e-a34b-93ee-d17b9c102a9d@yandex.ru \
--to=k2k@yandex.ru \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).