X-Spam-Check-By: sourceware.org
Message-ID: <813e5f920611270225i797ae9dauc5c2d0194d53005f@mail.gmail.com>
Date: Mon, 27 Nov 2006 21:25:46 +1100
From: "Hugh McMaster" <dasjournal AT gmail DOT com>
To: cygwin AT cygwin DOT com, "Mikkel Erup" <mikkelerup AT yahoo DOT com>
Subject: Re: 1.5.22: Error from anything using the cygwin dll
In-Reply-To: <426707.68970.qm@web52103.mail.yahoo.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <426707 DOT 68970 DOT qm AT web52103 DOT mail DOT yahoo DOT com>
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
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

Hi Mikkel,

I too have had this problem, as has another Cygwin user on this
mailing list.  I am now attempting to install Cygwin once more to
check whether this problem still exists.  If it does, it could be the
result of a recent change to a package.

I will let you know how things go.

Hugh

On 27/11/06, Mikkel Erup wrote:
> I get a message box with the following error trying to run
> any cygwin program:
>
> The instruction at "0x6100365f" referenced memory at
> "0x006ada90".
> The memory could not be "written".
>
> id.exe, bash.exe etc. All of them produce the error.
> Somtimes, like 1 out of 50 or less a program will succeed.
> For example I just ran uname from a windows command window
> and it worked the first time, then failed several times.
> Sometimes the cygwin.bat script will start the bash shell and not
> show the above message box. In that case the first lines read
> "5 [main] bash 3316 dll_crt0_1: internal error: couldn't
> determine location of thread function on stack. Expect signal
> errors.".
> Any commands from the bash shell will still produce the error
> message box described above, though.
> The setup program didn't succeed normally either because ash.exe
> and bash.exe crashed showing the message box described earlier.
> If I boot into safe mode cygwin works but not if I boot into
> safe mode with network.
> I tried killing all processes not vital to running Windows as
> well as stopping all services.
> Cygwin programs kept producing the error, though.
> Output from cygcheck -s -v -r is attached.

--
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/