public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Keith Christian <keith1christian@gmail.com>
To: Brian.Inglis@systematicsw.ab.ca, cygwin@cygwin.com
Subject: Re: Cygwin 2.6.1 bash fork errors upon starting mintty
Date: Mon, 26 Dec 2016 19:05:00 -0000	[thread overview]
Message-ID: <CAFWoy7FKQfqjPTYg+4b8Wriaq1jOGn2p+XxyRDikeL5tud8J=g@mail.gmail.com> (raw)
In-Reply-To: <4077531c-2c87-de22-57a4-c6546c51dda6@SystematicSw.ab.ca>

Brian,

Thanks, with all Cygwin processes stopped, opening an ash.exe window
via start/run, then cd /bin and running rebaseall fixed the errors
present when I start mintty.

Keith

On Mon, Dec 26, 2016 at 9:43 AM, Brian Inglis
<Brian.Inglis@systematicsw.ab.ca> wrote:
> On 2016-12-26 09:19, Keith Christian wrote:
>> I created a cygcheck -s -r -v file to attach, but sourceware dot org
>> blocked it
>
> Sourceware blocks all non-text emails - see below.
>
>> Updated Cygwin this morning, getting fork errors (even after
>> rebooting, (although reboots should not matter)) when starting
>> mintty:
>>       0 [main] bash 6072 child_info_fork::abort:
>> C:\cygwin\bin\cygncursesw-10.dll: Loaded to different address:
>> parent(0x75260000) != child(0x760000)
>> -bash: fork: retry: Resource temporarily unavailable
>>       1 [main] bash 11040 child_info_fork::abort:
>> C:\cygwin\bin\cygncursesw-10.dll: Loaded to different address:
>> parent(0x75260000) != child(0xEE0000)
>> -bash: fork: retry: No child processes
>
> Run "rebase-trigger fullrebase", shut down *ALL* Cygwin processes,
> download and run Setup.
>
>> CYGWIN_NT-10.0-WOW Keith-PC 2.6.1(0.305/5/3) 2016-12-16 11:50 i686 Cygwin
>
> If a full rebase does not fix it, you may have to uninstall some
> packages using Setup, and rerun the above process. You have limited
> address space under Cygwin 32 and may have to move to Cygwin 64.
>
>> Unfortunately, the cygcheck attachment was blocked by sourceware dot
>> org. What to do now?
>
> Ensure that your email is sent as text only and the attachment is sent
> as text - you may have to add .txt to cygcheck output file name to
> have it handled properly by your mail client.
>
> --
> 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
>

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

      reply	other threads:[~2016-12-26 19:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-26 16:19 Keith Christian
2016-12-26 16:43 ` Brian Inglis
2016-12-26 19:05   ` Keith Christian [this message]

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='CAFWoy7FKQfqjPTYg+4b8Wriaq1jOGn2p+XxyRDikeL5tud8J=g@mail.gmail.com' \
    --to=keith1christian@gmail.com \
    --cc=Brian.Inglis@systematicsw.ab.ca \
    --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).