This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: fork issue on Cygwin x86_64 2.10.0-1
- From: Tatsuro MATSUOKA <tmacchant2 at yahoo dot co dot jp>
- To: Heavenly Avenger <avenger at avenger dot ws>, cygwin at cygwin dot com
- Date: Fri, 20 Jul 2018 13:50:15 +0900 (JST)
- Subject: Re: fork issue on Cygwin x86_64 2.10.0-1
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=yj20110701; d=yahoo.co.jp; h=Message-ID:X-YMail-OSG:Received:X-Mailer:X-YMail-JAS:References:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=E7aQuXC8x991LthkkOJ9zEDSDo6A/cct15FKXBZVXyOzOK1kYZVZ2z5mkI64K4e9hNIoIuiuOyEyM6zbRh0Ap/uQcO3KOwyBjZZIP2DQ/y156S6vKx4MEIVPhMFZqX4xVcWu263B5D+vB36z5G9GpnWm8YCGfOIJUza3PqHEwU4=;
- References: <132992.64516.qm@web103106.mail.kks.yahoo.co.jp> <0d7146af-b0d0-2490-584e-a64c338f7903@avenger.ws>
- Reply-to: Tatsuro MATSUOKA <matsuoka at nuce dot nagoya-u dot ac dot jp>
>
> On 7/19/2018 9:25 PM, Tatsuro MATSUOKA wrote:
>> cygwin1.dll 2.10.0-1
>>
>> At log in bash cygwin does not work due to the below
>> 0 [main] bash 9888 child_info_fork::abort:
> C:\cygwin64\bin\cygncursesw-10.dll: Loaded to different address:
> parent(0x80000) != child(0x150000)
>>
>> I execute setup_x86_64.exe, execute autorebase.dash and reboot PC but the
> problem was not solved.
>>
>> Any suggestions?
>>
>> Tatsuro
----- Original Message -----
> From: Heavenly Avenger
> To: cygwin
> Cc:
> Date: 2018/7/20, Fri 09:38
> Subject: Re: fork issue on Cygwin x86_64 2.10.0-1
>
>t he rebaseall sometimes do not work because files are lock()ed by windows. So
> triple, no, quadruple check you have all cygwin processes stopped, including
> possible "cygrunsv" services, before you even let it play with
> autorebase.
>
> You can run again the cygsetup and make it reinstall the offending package, so
> that it runs rebase to it -- but it would be for naught if you still have stuff
> locking the rebased packages.
>
> This issue is really the thorn by cygwin's side for a long time... always,
> maybe?
>
> I wonder if this address limitation was just a "quick implementation"
> to be able to interface unix system calls to windows, or if it really is
> impossible to have cygwin's memory allocation be able to dynamically
> allocate stuff around the system without the need to reserve those base
> addresses and avoid conflicts, etc.
I executed reinstall on Cygwin setup, the issue was solved.
Thanks!
Tatsuro
--
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