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
>
>
Confir
> 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:
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:\
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
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
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 Wi
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
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
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 for
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 freque
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 ru
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
c
Hi!
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\b
13 matches
Mail list logo
