X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-1.1 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE,SPF_NEUTRAL
X-Spam-Check-By:	sourceware.org
X-Google-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding:x-gm-message-state; bh=1CAXMQrzFitD83FeGfV207dNq+K9Mp016P+YdCiEhNI=; b=A9bqgf5ZX9xBcrjm6OSYg2zsTqxMkSfLE/vCZ7B+iytGcxq00sa/XSN3X7JZvx8CHi RoxKiBgDcZE5XMHbIr2YwtGmbdV8OXPdFdTER46s+ydMJ9yuTT4l2tr8wZZCEAGtX4Wy SsHWOjTm54NH3RY3uKCCCWMJ3U6rGKw5m00EfDgUTUOumpLZkM3Xlazk4aMH1jLNwLep RD/L8NuDdHpqDep0sY7rY8MxfZvQQ+hXHicMe4Jlr6SnDyI2bBekipEDgf2f0OGGbyAn VwGCZQwODjhmxtZsCVDZwA0whZCs2EnrSgb9y5/KxUdH5eAh6kBv/5UxxoVRC41PBxN5 fCdA==
MIME-Version:	1.0
In-Reply-To:	<CABT-+2rgkM5rG7AFgxPev1vBd534+6q=NkV7-20-N-RAOH=TnQ@mail.gmail.com>
References:	<CABT-+2rFSA4V6eoS0f9a1RX7+cmk7NpkQBgGx5DSiHhBSThJyg AT mail DOT gmail DOT com> <CABT-+2rgkM5rG7AFgxPev1vBd534+6q=NkV7-20-N-RAOH=TnQ AT mail DOT gmail DOT 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 AT myuw DOT net>
To:	cygwin AT cygwin DOT com
X-Gm-Message-State:	ALoCoQlvLyq1D5bAKwA92mmtnp/lFgGf7oVwEd2bPABSc4Ec5/kMAB+PYW1efY0TREiRza4SQcSc
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id q3UCJRMO007012

> 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

- Raw text -