From: Fran Litterio <flitterio@gmail.com>
To: cygwin@cygwin.com
Subject: Re: bash shell gets aborts under latest Windows 10 updates as of 4/2/17
Date: Thu, 04 May 2017 16:52:00 -0000 [thread overview]
Message-ID: <oefm81$7f6$1@blaine.gmane.org> (raw)
In-Reply-To: <961799291.3143426.1491159192981@mail.yahoo.com>
On 4/2/2017 2:53 PM, gavin bowlby via cygwin wrote:
> I see the following when trying to open a Cygwin bash shell on my Win10 PC after applying updates today, 4/2/2017; I didn't see this before the latest Win10 update:
>
> 0 [main] bash 11884 child_info_fork::abort: C:\cygwin\bin\cygiconv-2.dll: Loaded to different address: parent(0xFA0000) != child(0xE80000)
> -bash: fork: retry: No child processes
I believe this is a classic case where rebasing is required. See
https://stackoverflow.com/questions/33125842/what-does-rebaseall-in-cygwin-do
for details. Sometimes the problem can be fixed by rebooting and
starting a Cygwin app (e.g., Bash) very soon after boot (so that the
DLLs get loaded at their preferred addressed), but that is a temporary
workaround.
You can rebase all the DLLs as follows:
- Terminate _all_ Cygwin apps (don't forget about daemons like sshd).
- Open a Command Prompt.
- Run "ash" (a shell included with Cygwin). Do not run "bash".
- Enter command "rebaseall".
- I usually follow this with a reboot, but that may not be necessary.
Hope this helps.
--
Fran
--
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:[~2017-05-04 16:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <961799291.3143426.1491159192981.ref@mail.yahoo.com>
2017-04-02 18:53 ` gavin bowlby via cygwin
2017-04-02 20:20 ` gavin bowlby via cygwin
2017-05-04 16:52 ` Fran Litterio [this message]
2017-05-05 11:35 ` Andrey Repin
2017-05-05 12:24 ` Fran Litterio
2017-05-05 12:35 ` Andrey Repin
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='oefm81$7f6$1@blaine.gmane.org' \
--to=flitterio@gmail.com \
--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).