X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=BhSXTwipgNfmo7VfKT+nV9iLaaIWLRqZeFP+U89K2TDq0FgIp/aRn
	T0ypEtZijSOc5ukNrENhVumNfphgKRgdd64juZuv0jjZnSl298DEgK4EHthHn9bN
	BcmzY1dn4SeWLq6kVoU4LKHNSKLfqqx9Py2oIdkZxesgjSOQYMWvJ0=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; s=default;
	bh=wd9RtTNpBStkHitzaGADNimSZP8=; b=peOCGuevq7jGti45Rp4+0F9LwVYL
	Ju4B/QrwF0WMizTAe/4DiDM0Kkh0FsdK5CpbtdiFzML9/Nm4GBP05qSigjE+yuco
	PchO6jjiLm07DMv2g0M/GdaMu07g8sv4Le7E+FXrOVpxYQKIkFNgW+7NsZ0b09zX
	7AuO650jTTTy9rg=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.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
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=-1.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2
X-HELO:	mho-01-ewr.mailhop.org
X-Mail-Handler:	Dyn Standard SMTP by Dyn
X-Report-Abuse-To:	abuse AT dyndns DOT com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User:	U2FsdGVkX1+sl1UH8HUH7lAa1pj0YQYi
Date:	Fri, 31 Jan 2014 11:38:45 -0500
From:	Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: unable to run any cygwin commands: error while loading shared libraries: C
Message-ID:	<20140131163845.GB5169@ednor.casa.cgf.cx>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<CAK3chpAeWayzSs8-X7oj91S2m9rW6uo0Pzxj+8=yiVNwRgBmiQ AT mail DOT gmail DOT com> <52D706D7 DOT 7000704 AT cygwin DOT com> <CAK3chpDqUBbJDBFW6ww4LFGr5=3wLdZRDvZFD+aGnJqzsJubnA AT mail DOT gmail DOT com> <52D80F74 DOT 3030905 AT cygwin DOT com> <CAK3chpBXoEyXOEsQdcVExMMDoVs=eH1MOjp_MV5PBJ6qZ=jy5g AT mail DOT gmail DOT com>
MIME-Version:	1.0
In-Reply-To:	<CAK3chpBXoEyXOEsQdcVExMMDoVs=eH1MOjp_MV5PBJ6qZ=jy5g@mail.gmail.com>
User-Agent:	Mutt/1.5.20 (2009-06-14)

On Fri, Jan 31, 2014 at 03:45:35PM +0000, Mateusz Malinowski wrote:
>I'm pretty sure that it's not a problem with  BLODA. I checked
>bash.exe in Dependency Walker. I managed to fix some errors with DLLs
>(it shows more info than cygcheck), nevertheless, I still had the same
>problem. So then I run profiler on bash.exe and later only on
>cygwin1.dll to make sure that results are real. See for yourselves:
>...
>LoadLibraryW("C:\Windows\
>system32\user32.dll") called from
>"CYGWIN1.DLL" at address 0x0000000180041DE4.
>LoadLibraryW("C:\Windows\system32\user32.dll") returned 0x00000000769A0000.
>GetProcAddress(0x00000000769A0000 [USER32.DLL], "EnumWindows") called
>from "CYGWIN1.DLL" at address 0x0000000180041C76 and returned
>0x00000000769B5E28.
>GetProcAddress(0x00000000769A0000 [USER32.DLL], "GetKeyboardLayout")
>called from "CYGWIN1.DLL" at address 0x0000000180041C76 and returned
>0x00000000769B6610.
>LoadLibraryW("\\?\C:\cygwin64\bin\C") called from "CYGWIN1.DLL" at
>address 0x00000001800B9FAC.
>LoadLibraryW("\\?\C:\cygwin64\bin\C") returned NULL. Error: The
>specified module could not be found (126).
>Exited "BASH.EXE" (process 0xA10) with code 256 (0x100).
>
>Does anyone know why it tries to load C:\cygwin64\bin\C (full output
>from profiler in attached file)?

What is your theory about the problem if this isn't something specific
to your computer, i.e., BLODA?  Obviously the vast majority of our
community is able to run bash.  That points to something running in
the background or misconfigured on your end.  If you had to fix some
errors with DLLs then something is really wrong.

cgf

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

- Raw text -