From: Stan Berka <sberka@poptal.com>
To: cygwin@cygwin.com
Subject: Error when starting Cygwin shell: init_cygheap error
Date: Fri, 01 Mar 2002 17:55:00 -0000 [thread overview]
Message-ID: <20020302.1535534@mis.configured.host> (raw)
Hi,
I have the same problem as in the January thread cited below:
when starting the Cygwin shell I'm getting an error:
9 [main] bash 2040 init_cygheap::etc_changed: Can't open /etc for
checking, Win32 error 1
I have checked that I don't have two cygwin1.dll in my PATH. When I
rename the cygwin1.dll in the /bin directory to something else, I'm
getting a message that cygwin1.dll is missing. So what can be the
problem?
BTW, when I do "which cygwin1.dll" from the shell it tells me:
/usr/bin/cygwin1.dll
There is no /usr/bin. Is this a part of the problem?
Stan Berka, Pope & Talbot Inc.
---- Thread about the same problem ----
From: Corinna Vinschen
To: cygwin at cygwin dot com
Date: Thu, 10 Jan 2002 15:08:51 +0100
Subject: Re: Cygwin 1.3.6 on NT 4.0: init_cygheap error
References: <3C3D8B15.4D0A49C7@email.sps.mot.com>
<3C3D9EA8.5070101@syntrex.com>
On Thu, Jan 10, 2002 at 03:01:12PM +0100, Pavel Tsekov wrote:
> Markus Brenner wrote:
> >For compatibility and historical reasons the B20 release is also
installed
> >on the same machine (I am not sure whether this has any influence on the
> >above described problem).
>
>
> This is not good. I'm not 100 % sure if this is connected to your
^^^^^^^^^^^^^^^^^
Right! Never have two copies of cygwin1.dll in the DLL search path.
Even worse if they have diverging versions.
Corinna
--------------
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next reply other threads:[~2002-03-02 1:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-01 17:55 Stan Berka [this message]
2002-03-04 8:43 ` Larry Hall (RFK Partners, Inc)
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=20020302.1535534@mis.configured.host \
--to=sberka@poptal.com \
--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).