MIME-Version: 1.0
In-Reply-To: <CABT-+2rgkM5rG7AFgxPev1vBd534+6q=NkV7-20-N-RAOH=TnQ@mail.gmail.com>
References: <CABT-+2rFSA4V6eoS0f9a1RX7+cmk7NpkQBgGx5DSiHhBSThJyg@mail.gmail.com>	<CABT-+2rgkM5rG7AFgxPev1vBd534+6q=NkV7-20-N-RAOH=TnQ@mail.gmail.com>
Date: Mon, 30 Apr 2012 05:19:04 -0700
Message-ID: <CABT-+2qo-Ee3fdzdD1_Jh0=6fWRNFu=Fw-he25=_3anZfW+iNA@mail.gmail.com>
Subject: Re: Cygwin errors after altering Windows command prompt shortcut (???)
From: Pat Tressel <ptressel@myuw.net>
To: cygwin@cygwin.com
Content-Type: text/plain; charset=ISO-8859-1
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Content-Transfer-Encoding: 8bit

> bash-4.1$ ls
>       0 [main] bash 8316 child_info_fork::abort: cygreadline7.dll: Loaded to different address: parent(0x3C0000) != child(0x320000)
> bash: fork: retry: Resource temporarily unavailable
>       0 [main] bash 7708 child_info_fork::abort: cygreadline7.dll: Loaded to different address: parent(0x3C0000) != child(0x320000)
> bash: fork: retry: Resource temporarily unavailable
>
> Starting a new Cygwin shell instance got errors from bash before entering a command.

Forget those other things that might have been possible causes -- they
now look like red herrings.  This happened again recently, once after
the system hibernated, and once after a reboot.  (In the second case,
I believe there were no Cygwin windows open when the system was shut
down, but it's possible that the process had not finished exiting and
was killed by shutdown.)

Recall from the previous occurrence that restoring from the last
restore point caused the error to go away, but that's not a good
workaround, as it takes at least half an hour to make a restore point
or restore from it, and restoring throws away anything installed since
the last restore point.

This is a very recent version of Cygwin -- it was updated 6 days ago.

Any ideas what might be wrong?  Perhaps something that wasn't cleaned
up during shutdown if the process did get killed?

Thanks!

-- Pat

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