Re: unable to run any cygwin commands: error while loading shared libraries: C

[Mateusz Malinowski <mateusz dot tomasz dot malinowski at gmail dot com>]

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

Many thanks,
Mateusz

2014-01-16 Larry Hall:
> On 1/16/2014 4:33 AM, Mateusz Malinowski wrote:
>>
>> 2014/1/15 Larry Hall:
>>>
>>> On 1/15/2014 10:11 AM, Mateusz Malinowski wrote:
>>>>
>>>>
>>>> Hello,
>>>>
>>>> I have a problem similar to one described in "error while loading
>>>> shared libraries: ?: cannot open shared object file: No such file or
>>>> directory" thread, though in my case I can't run any cygwin commands
>>>> (i.e. I can't even open cygwin's bash).
>>>
>>>
>>>
>>> So you're clearly missing a DLL.  Presuming your installation went
>>> OK and you saw no complaints from the postinstall scripts, try
>>> 'cygcheck bash' and see if it complains about some missing DLL(s).
>>> If it does, use cygcheck or 'http://cygwin.com/packages/' to find the
>>> package with that DLL.  Install that/those packages.
>>
>>
>>>> I am aware that in that thread the problem was solved due to
>>>> anti-software, however; in my company we all use the same anti-virus
>>>> and I'm the only one having this issue with cygwin. I uploaded
>>>> cygcheck.out and cygcheck.err files together with stackdumfiles (it
>>>> couldn't execute id and cygrunsrv), in case they might be helpful
>>>> (couldn't send them attached due to 552 spam score):
>>>> http://speedy.sh/QR2QZ/files.zip
>>>
>>>
>>>
>>> If 'id' won't run, this makes me think your installation failed.  You
>>> can try just rerunning 'setup*.exe' and reinstall.   Watch for errors.
>>
>>
>> As I said, I don't have any errors while installing cygwin.
>
>
> Perhaps you need to find and look at setup.log and setup.log.full.
>
>
>>>> Cygwin worked normally for me in the past. I believe that something
>>>> might have messed up when I was installing some other software on my
>>>> machine, but I have no idea what it might have been. I tried to delete
>>>> cygwin and manually clear all references to it in the register, but
>>>> still, after installing, it doesn't work.
>>>
>>>
>>>
>>> OK, I get the same feeling as I mentioned above from this.
>>>
>>>
>>>> Also the interesting thing is that cygcheck reports 3 cygwin1.dll,
>>>> although there is only one on my machine.
>>>
>>>
>>>
>>> As long as they all reference the same DLL in the same physical location
>>> (mount paths not-withstanding), that's fine.
>>>
>>>
>>>> I'm looking forward to any solution anyone can provide. I must admit
>>>> that I ran out of options.
>>>
>>>
>>>
>>> If none of the above helps, please *attach* 'cygcheck -srv' output to
>>> any follow-up.  I tried to look at the zip file you reference above but
>>> it is invalid.
>>
>>
>> Ok, this upload site seems a bit dodgy. I try to attach .out file again.
>
>
> Yes, that came through fine.  OK, other than the obvious omissions that
> are expected because things like 'id' won't run, this looks OK.  So this
> points back to BLODA if none of my previous suggestions shed any light
> on the situation.  If the BLODA in question isn't something you can
> uninstall or turn off, perhaps it will allow you to tell it to ignore
> stuff in c:\cygwin64?
>
> --
> Larry
>
> _____________________________________________________________________
>
>
> A: Yes.
>> Q: Are you sure?
>>> A: Because it reverses the logical flow of conversation.
>>>> Q: Why is top posting annoying in email?
>
> --
> 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
>

Attachment: profiler_bash.txt
Description: Text document

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