All clear (was Re: 2012-03-19 snapshot problematic (was Re: cygwin-1.7.10-1 fork - address space needed by ... already in use))

marco atzeri marco.atzeri@gmail.com
Wed Mar 21 05:44:00 GMT 2012


On 3/21/2012 5:41 AM, marco atzeri wrote:
> On 3/21/2012 12:56 AM, Christopher Faylor wrote:
>> On Tue, Mar 20, 2012 at 01:10:51AM -0400, Christopher Faylor wrote:
>>> On Mon, Mar 19, 2012 at 04:54:33PM -0400, Christopher Faylor wrote:
>>>> [snip]
>>>> Thanks for the cygcheck output.
>>>>
>>>> I was never able to duplicate the problem so I rewrote the way this was
>>>> handled. The error message is completely gone now.
>>>>
>>>> With luck you won't see anything like this now.
>>>
>>> My change to fix this problem did something bad to process
>>> syncronization. I have the beginnings of a fix in my sandbox
>>> but I'm not quite ready to check anything in.
>>>
>>> In the meantime, I'd advise against using the 2012-03-19 snapshot.
>>
>> The latest snapshot should now be ok.
>>
>> http://cygwin.com/snapshots/
>>
>> cgf
>>
>
> unfortunately no
> dash+rebaseall shows:
>
> 0 [waitproc] dash 6868! proc_waiter: error on read of child wait pipe 0x0,
> Win32 error 6
>
> and the process never complete.
>
>
> $ uname -a
> CYGWIN_NT-6.1-WOW64 MARCOATZERI 1.7.12s(0.260/5/3) 20120320 23:14:21
> i686 Cygwin
>

I guess I was to fast...

$ uname -a
CYGWIN_NT-6.1-WOW64 MARCOATZERI 1.7.12s(0.260/5/3) 20120321 05:24:00 
i686 Cygwin


this seems fine

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



More information about the Cygwin mailing list