Re: Random "child_info_fork::abort:"

2016-10-15 Thread Evgeny Grin
On 15.10.2016 1:58, Tony Kelman wrote:
>>   2 [main] mandb (736) t:\cygwin64\bin\mandb.exe: *** fatal error -
>> cygheap base mismatch detected - 0x1802FC408/0x110C408.
> 
> As far as I can tell, build 14946 fixed whatever the problem was.
> Crisis averted, for now.
> 
> -Tony
> 
> 

Confirming. Windows build 14946 is fine.
Cygwin64, Msys2 (both x32 and x64) now works correctly.
As well as Msys2-based tools, like git for windows.

May be that was a bug in Windows: FreeLibrary() unload wrong .DLL image
with same filename. Suspect that it's not a typical situation for
developers of Windows when some app/lib sequentially loads/unloads same
.DLL but on different positions. As Windows actually unload .DLLs after
some delay - it just unloaded wrong image. That's my guessing.

--
Best Wishes,
Evgeny Grin

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



Re: Random "child_info_fork::abort:"

2016-10-14 Thread Tony Kelman
>  2 [main] mandb (736) t:\cygwin64\bin\mandb.exe: *** fatal error -
> cygheap base mismatch detected - 0x1802FC408/0x110C408.

As far as I can tell, build 14946 fixed whatever the problem was.
Crisis averted, for now.

-Tony

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



Re: Random "child_info_fork::abort:"

2016-10-13 Thread Evgeny Grin
On 13.10.2016 19:58, Evgeny Grin wrote:
> On 13.10.2016 18:24, Evgeny Grin wrote:
> 
> What I got from strace (typical output):
> 
>  649705 [main] mandb 6288 child_info::sync: n 2, waiting for
> subproc_ready(0x280) and child process(0x1CC)
>6358 [main] mandb 7888 child_info_fork::abort:
> T:\cygwin64\bin\cyggdbm-4.dll: Loaded to different address:
> parent(0x1FFFC51) != child(0x15)
> --- Process 7888 created
> --- Process 7888 loaded C:\Windows\System32\ntdll.dll at 7FFE2FF7
> --- Process 7888 loaded C:\Windows\System32\kernel32.dll at 7FFE2D60
> --- Process 7888 loaded C:\Windows\System32\KernelBase.dll at
> 7FFE2C73
> --- Process 7888 thread 912 created
> --- Process 7888 thread 10792 created
> --- Process 7888 loaded T:\cygwin64\bin\cygmandb-2-7-5.dll at
> 01FFFB8F
> --- Process 7888 loaded T:\cygwin64\bin\cygwin1.dll at 00018004
> --- Process 7888 loaded T:\cygwin64\bin\cygintl-8.dll at 0003FBB9
> --- Process 7888 thread 14024 created
> --- Process 7888 loaded T:\cygwin64\bin\cygiconv-2.dll at 0003FBBF
> --- Process 7888 loaded T:\cygwin64\bin\cygpipeline-1.dll at
> 01FFFB47
> --- Process 7888 loaded T:\cygwin64\bin\cygman-2-7-5.dll at 01FFFB90
> --- Process 7888 loaded T:\cygwin64\bin\cyggdbm-4.dll at 0015
> --- Process 7888 loaded T:\cygwin64\bin\cygman-2-7-5.dll at 0017
> --- Process 7888 unloaded DLL at 0017
> --- Process 7888 loaded T:\cygwin64\bin\cygz.dll at 01FFFACF
> --- Process 7888 loaded T:\cygwin64\bin\cyggdbm-4.dll at 01FFFC51
> --- Process 7888 unloaded DLL at 01FFFC51
>6358 [main] mandb 7888 child_info_fork::abort:
> T:\cygwin64\bin\cyggdbm-4.dll: Loaded to different address:
> parent(0x1FFFC51) != child(0x15)
> --- Process 7888 thread 14024 exited with status 0x80
> --- Process 7888 thread 10144 exited with status 0x80
> --- Process 7888 thread 10792 exited with status 0x80
> --- Process 7888 exited with status 0x80
>  663649 [main] mandb 6288 child_info::sync: pid 7888, WFMO returned 1,
> exit_code 0x80, res 0
>  663743 [main] mandb 6288 sig_send: sendsig 0xD8, pid 6288, signal -73,
> its_me 1
>  663771 [main] mandb 6288 sig_send: wakeup 0x2EC
>  663800 [main] mandb 6288 sig_send: Waiting for pack.wakeup 0x2EC
>  663840 [sig] mandb 6288 wait_sig: signalling pack.wakeup 0x2EC
>  663886 [main] mandb 6288 sig_send: returning 0x0 from sending signal -73
> mandb: fork failed: Resource temporarily unavailable
> 
> 
> The cyggdbm-4.dll is loaded two times: at 0x15 and at 0x1FFFC51,
> but for some reason unloaded from 0x1FFFC51.
> This looks like a bug in cygwin.
> 

Incorrect cygwin dll unloaded:

 837063 [main] mandb 5504 child_info::sync: n 2, waiting for
subproc_ready(0x10C) and child process(0x1E4)
--- Process 736 created
--- Process 736 loaded C:\Windows\System32\ntdll.dll at 7FFE2FF7
--- Process 736 loaded C:\Windows\System32\kernel32.dll at 7FFE2D60
--- Process 736 loaded C:\Windows\System32\KernelBase.dll at
7FFE2C73
--- Process 736 thread 8588 created
--- Process 736 thread 14860 created
--- Process 736 loaded T:\cygwin64\bin\cyggdbm-4.dll at 01FFFC51
--- Process 736 thread 10128 created
--- Process 736 loaded T:\cygwin64\bin\cygmandb-2-7-5.dll at
01FFFB8F
--- Process 736 loaded T:\cygwin64\bin\cygiconv-2.dll at 0003FBBF
--- Process 736 loaded T:\cygwin64\bin\cygintl-8.dll at 0003FBB9
--- Process 736 loaded T:\cygwin64\bin\cygpipeline-1.dll at 01FFFB47
--- Process 736 loaded T:\cygwin64\bin\cygman-2-7-5.dll at 01FFFB90
--- Process 736 loaded T:\cygwin64\bin\cygwin1.dll at 00018004
--- Process 736 loaded T:\cygwin64\bin\cygwin1.dll at 00E5
--- Process 736 loaded T:\cygwin64\bin\cygwin1.dll at 019D
--- Process 736 loaded T:\cygwin64\bin\cygwin1.dll at 0141
--- Process 736 loaded T:\cygwin64\bin\cygz.dll at 01FFFACF
--- Process 736 unloaded DLL at 019D
--- Process 736 unloaded DLL at 0141
--- Process 736 unloaded DLL at 00018004
  2 [main] mandb (736) t:\cygwin64\bin\mandb.exe: *** fatal error -
cygheap base mismatch detected - 0x1802FC408/0x110C408.


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



Re: Random "child_info_fork::abort:"

2016-10-13 Thread Evgeny Grin
On 13.10.2016 18:24, Evgeny Grin wrote:
> On 13.10.2016 10:11, Evgeny Grin wrote:
>> On 12.10.2016 21:45, Evgeny Grin wrote:
>>> On 12.10.2016 13:59, Evgeny Grin wrote:
 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(0x3FEAB) != child(0x1C)
>> 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(0x19) != child(0x3FB70)

> 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.
>>>
>>> Additionally tested under VM.
>>> Clear install of Windows 10 x64 14931 (US English), VM guest tools and
>>> Cygwin x64. First run of man-db - same error.
>>> Need new workarounds?
>>> Seems that will be in all new builds.
>>
>> Same happens with new Windows build 14942.
>> Both Cygwin and Msys2 is not usable anymore.
>>
>> MS is pushing us to "Ubuntu on Windows"?
>>
> 
> When trying to actively use cygwin, got same (as in Msys2) errors:
> 
>  *** fatal error - cygheap base mismatch detected - 0x180302408/0x1082408.
> 
> Is it because of cygwin.dll loaded on incorrect address?
> 

What I got from strace (typical output):

 649705 [main] mandb 6288 child_info::sync: n 2, waiting for
subproc_ready(0x280) and child process(0x1CC)
   6358 [main] mandb 7888 child_info_fork::abort:
T:\cygwin64\bin\cyggdbm-4.dll: Loaded to different address:
parent(0x1FFFC51) != child(0x15)
--- Process 7888 created
--- Process 7888 loaded C:\Windows\System32\ntdll.dll at 7FFE2FF7
--- Process 7888 loaded C:\Windows\System32\kernel32.dll at 7FFE2D60
--- Process 7888 loaded C:\Windows\System32\KernelBase.dll at
7FFE2C73
--- Process 7888 thread 912 created
--- Process 7888 thread 10792 created
--- Process 7888 loaded T:\cygwin64\bin\cygmandb-2-7-5.dll at
01FFFB8F
--- Process 7888 loaded T:\cygwin64\bin\cygwin1.dll at 00018004
--- Process 7888 loaded T:\cygwin64\bin\cygintl-8.dll at 0003FBB9
--- Process 7888 thread 14024 created
--- Process 7888 loaded T:\cygwin64\bin\cygiconv-2.dll at 0003FBBF
--- Process 7888 loaded T:\cygwin64\bin\cygpipeline-1.dll at
01FFFB47
--- Process 7888 loaded T:\cygwin64\bin\cygman-2-7-5.dll at 01FFFB90
--- Process 7888 loaded T:\cygwin64\bin\cyggdbm-4.dll at 0015
--- Process 7888 loaded T:\cygwin64\bin\cygman-2-7-5.dll at 0017
--- Process 7888 unloaded DLL at 0017
--- Process 7888 loaded T:\cygwin64\bin\cygz.dll at 01FFFACF
--- Process 7888 loaded T:\cygwin64\bin\cyggdbm-4.dll at 01FFFC51
--- Process 7888 unloaded DLL at 01FFFC51
   6358 [main] mandb 7888 child_info_fork::abort:
T:\cygwin64\bin\cyggdbm-4.dll: Loaded to different address:
parent(0x1FFFC51) != child(0x15)
--- Process 7888 thread 14024 exited with status 0x80
--- Process 7888 thread 10144 exited with status 0x80
--- Process 7888 thread 10792 exited with status 0x80

Re: Random "child_info_fork::abort:"

2016-10-13 Thread Evgeny Grin
On 13.10.2016 10:11, Evgeny Grin wrote:
> On 12.10.2016 21:45, Evgeny Grin wrote:
>> On 12.10.2016 13:59, Evgeny Grin wrote:
>>> 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(0x3FEAB) != child(0x1C)
> 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(0x19) != child(0x3FB70)
>>>
 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.
>>
>> Additionally tested under VM.
>> Clear install of Windows 10 x64 14931 (US English), VM guest tools and
>> Cygwin x64. First run of man-db - same error.
>> Need new workarounds?
>> Seems that will be in all new builds.
> 
> Same happens with new Windows build 14942.
> Both Cygwin and Msys2 is not usable anymore.
> 
> MS is pushing us to "Ubuntu on Windows"?
> 

When trying to actively use cygwin, got same (as in Msys2) errors:

 *** fatal error - cygheap base mismatch detected - 0x180302408/0x1082408.

Is it because of cygwin.dll loaded on incorrect address?

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



Re: Random "child_info_fork::abort:"

2016-10-13 Thread Brian Inglis

On 2016-10-13 06:31, Eliot Moss wrote:

On 10/13/2016 8:00 AM, Marco Atzeri wrote:

On 13/10/2016 09:11, Evgeny Grin wrote:

MS is pushing us to "Ubuntu on Windows"?

Interesting. Are we back to the old tactics ?
https://en.wikipedia.org/wiki/AARD_code

I don't see the motivation.  We still buy Windows.
Do you think they'll charge extra for UoW?


Nope - they always need a POSIX subsystem available in some form
in order to satisy US Fed government requirements for mandatory
POSIX compatibility on all systems contract bids, even if few
will ever use that capability on their desktops or servers.

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



Re: Random "child_info_fork::abort:"

2016-10-13 Thread Eliot Moss

On 10/13/2016 8:00 AM, Marco Atzeri wrote:

On 13/10/2016 09:11, Evgeny Grin wrote:



MS is pushing us to "Ubuntu on Windows"?



Interesting. Are we back to the old tactics ?

https://en.wikipedia.org/wiki/AARD_code


I don't see the motivation.  We still buy Windows.
Do you think they'll charge extra for UoW?

Regards - Eliot Moss

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



Re: Random "child_info_fork::abort:"

2016-10-13 Thread Marco Atzeri

On 13/10/2016 09:11, Evgeny Grin wrote:


Additionally tested under VM.
Clear install of Windows 10 x64 14931 (US English), VM guest tools and
Cygwin x64. First run of man-db - same error.
Need new workarounds?
Seems that will be in all new builds.


Same happens with new Windows build 14942.
Both Cygwin and Msys2 is not usable anymore.

MS is pushing us to "Ubuntu on Windows"?



Interesting. Are we back to the old tactics ?

https://en.wikipedia.org/wiki/AARD_code

Regards
Marco


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



Re: Random "child_info_fork::abort:"

2016-10-13 Thread Evgeny Grin
On 12.10.2016 21:45, Evgeny Grin wrote:
> On 12.10.2016 13:59, Evgeny Grin wrote:
>> 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(0x3FEAB) != child(0x1C)
 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(0x19) != child(0x3FB70)
>>
>>> 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.
> 
> Additionally tested under VM.
> Clear install of Windows 10 x64 14931 (US English), VM guest tools and
> Cygwin x64. First run of man-db - same error.
> Need new workarounds?
> Seems that will be in all new builds.

Same happens with new Windows build 14942.
Both Cygwin and Msys2 is not usable anymore.

MS is pushing us to "Ubuntu on Windows"?

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



Re: Random "child_info_fork::abort:"

2016-10-12 Thread Evgeny Grin
On 12.10.2016 13:59, Evgeny Grin wrote:
> 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(0x3FEAB) != child(0x1C)
>>> 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(0x19) != child(0x3FB70)
> 
>> 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.

Additionally tested under VM.
Clear install of Windows 10 x64 14931 (US English), VM guest tools and
Cygwin x64. First run of man-db - same error.
Need new workarounds?
Seems that will be in all new builds.

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



Re: Random "child_info_fork::abort:"

2016-10-12 Thread Evgeny Grin
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(0x3FEAB) != child(0x1C)
>> 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(0x19) != child(0x3FB70)

> 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



Re: Random "child_info_fork::abort:"

2016-10-12 Thread Brian Inglis

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(0x3FEAB) != child(0x1C)
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