From: Eliot Moss <moss@cs.umass.edu>
To: cygwin <cygwin@cygwin.com>
Subject: Re: cygwin stopped working
Date: Wed, 14 Feb 2018 07:53:00 -0000 [thread overview]
Message-ID: <22a9e6d9-130f-31f1-9595-1914eef78252@cs.umass.edu> (raw)
In-Reply-To: <CAO+c-kGTqnhtbzY=jKNvtOrqgm76sA0J5zx7Gd4b8Jow=DM5PA@mail.gmail.com>
On 2/13/2018 8:41 PM, Bryan Zimmer wrote:
> I have been following this thread closely as I have a similar problem. It
> only differs in that mintty, which I use to start bash, fails completely.
> It tells me that it cannot fork, that the problem could be that I have more
> than 1 cygwin1.dll, that I should run rebaseall or rebase --help.
> Unfortunately all cygwin processes have the same problem. Even a fresh,
> clean re-installation of all of cygwin left me with the same problem.
I would assume you have - but just checking - have you looked really
hard for a second cygwin1.dll lurking somewhere? Reinstalling, etc.,
won't fix that ...
Regards - Eliot Moss
--
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
next prev parent reply other threads:[~2018-02-14 7:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-11 8:18 Andreas Schiffler
2018-02-11 10:42 ` Doug Henderson
2018-02-12 1:16 ` Andreas Schiffler
2018-02-12 2:30 ` Brian Inglis
2018-02-12 16:48 ` Jostein Berntsen
2018-02-13 4:58 ` Andreas Schiffler
2018-02-14 1:42 ` Bryan Zimmer
2018-02-14 7:53 ` Eliot Moss [this message]
2018-02-14 8:49 ` Marco Atzeri
2018-02-14 3:25 ` W10 Mandatory ASLR default (was: cygwin stopped working) Brian Inglis
2018-02-14 7:17 ` W10 Mandatory ASLR default Thomas Wolff
2018-02-14 7:36 ` Andreas Schiffler
2018-02-16 6:41 ` Brian Inglis
2018-02-18 19:43 ` Andreas Schiffler
2018-02-18 20:07 ` Achim Gratz
2018-02-18 22:40 ` Brian Inglis
2018-02-12 18:16 ` cygwin stopped working Achim Gratz
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=22a9e6d9-130f-31f1-9595-1914eef78252@cs.umass.edu \
--to=moss@cs.umass.edu \
--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).