1.5.21-1 - Crash on anything using cygwin1.dll
Thu Sep 28 17:08:00 GMT 2006
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
>>>> Life is short - so eat dessert first!
>>>> Eric Blake email@example.com
>>> 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 firstname.lastname@example.org
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
More information about the Cygwin