X-Spam-Check-By: sourceware.org
Message-ID: <451C01A8.8000103@gmail.com>
Date: Thu, 28 Sep 2006 12:08:56 -0500
From: OverlordQ <overlordq AT gmail DOT com>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: 1.5.21-1 - Crash on anything using cygwin1.dll
References: <451B4A0A DOT 3000100 AT gmail DOT com> <451B4C22 DOT 4040103 AT cygwin DOT com> <451B5213 DOT 60104 AT gmail DOT com> <451B5332 DOT 6010408 AT byu DOT net> <451B5946 DOT 2010503 AT gmail DOT com> <451BB8CD DOT 9070301 AT byu DOT net>
In-Reply-To: <451BB8CD.9070301@byu.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
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

Eric Blake wrote:
> According to overlordq AT gmail DOT com on 9/27/2006 11:10 PM:
>                       ^^^^     ^^^^^
> Consider updating your mail account to associate a real name to your email
> address, so that we don't accidentally quote it raw in replies.
> 
>>>> All others?  That sounds fishy right there; you should never have had more
>>>> than one in the first place if you wanted sane operational behavior.
>>>> Complete output from cygcheck would really be useful (just click past any
>>>> failure boxes that come up from trying to invoke id or other cygwin
>>>> subprocesses).
>>>>
>>>> --
>>>> Life is short - so eat dessert first!
>>>>
>>>> Eric Blake             ebb9 AT byu DOT net
>>> oops I lied dwwin killed it prematurely, here's the rest of the output:
> 
> Please ATTACH, not paste inline, so that the archive search engine does
> not get false positives.

Sorry about that.

>>> Not Found: sh
> 
> Did you kill the ash or bash postinstall script?  They copy /bin/bash.exe
> to /bin/sh.exe, and if that does not happen, cygwin will be pretty
> unusable.  It would be nice to figure out why that didn't happen.

Like I said in the original post, the post-install scripts cant run,
since . . . well bash crashes.

> Other than that, nothing jumped out at me as an obvious source of your
> problems, but it could be that there is still some other service using an
> older version of the .dll still loaded in memory.  Have you rebooted since
> you deleted other copies of cygwin1.dll?

Yes, still same problem.  And the other copies were from programs that
had been compiled under cygwin like Winboard, jtr, and a few Chess engines.

> --
> Life is short - so eat dessert first!
> 
> Eric Blake             ebb9 AT byu DOT net

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/