> From: "Larry Hall (Cygwin)" <reply-to-list-only-lh at cygwin dot com> > To: cygwin at cygwin dot com, > Date: 05/29/2013 03:51 PM > Subject: Re: Postinstall Script Errors With Exit Code 128 > Sent by: cygwin-owner at cygwin dot com > > On 5/29/2013 3:18 PM, Paul.Nickerson at desknetinc dot com wrote: > > So, I think that one of these functions hangs when > > cygwin1.dll is present. I'm thinking dump_dodgy_apps. > > Possibly. You may have a BLODA problem ( http://cygwin.com/acronyms/#BLODA), > whether known or unknown. If so, getting rid of it will certainly help. > > > I tried copying cygcheck.exe to other directories and leaving cygwin1.dll > > in bin, and cygcheck does not hang when run from other directories. > > Interesting. Maybe there's some Windows permission problems in the > directory you were running from?
I have fixed it. Thank you for your help. I have a few other AWS EC2 instances. One other was having trouble with Cygwin install, and none of the rest were. I tried comparing installed applications, but got nowhere. I also tried installing Windows updates on the troubled system, and copying the cygwin from a healthy system to the troubled one. Neither attempt worked. I had looked into folder permissions before, which all looked fine, and tried installing to another folder and even another drive, but that hadn't helped. I then used WinDbg to run C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/000-cygwin-post-install.sh", and I think I got this error: SetContext failed, 0x8007001F. Looking online, it seems that code is associated with "A device attached to the system is not functioning". I have already rebooted a bunch of times. I used Belarc Advisor to grab the virtual hardware version. Belarc Advisor said the System Model / Main Circuit Board / BIOS on both troubled instances was "Xen HVM domU 3.1.2-92.1.13.el5.", while on the other working instances it was "Xen HVM domU 3.4.3-2.6.18 09/01/2012". So, I shut down the instance (I use EBS volumes), created an AMI from it, created an Instance from the AMI, and started up that instance. This has the effect of applying a new virtual hardware if available (proven by the fact that I get a new Instance ID), as well as moving to different physical hardware. After this, Belarc Advisor reported the good virtual hardware version. And, I was able to successfully install and use Cygwin normally. :) I have attached the output of running that bash.exe command inside WinDbg, just in case it's useful for anything. Again, thank you for you help. ~ Paul
Microsoft (R) Windows Debugger Version 6.4.0007.2 Copyright (c) Microsoft Corporation. All rights reserved. CommandLine: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/000-cygwin-post-install.sh" Symbol search path is: C:\cygwin\usr\lib\debug\usr\bin Executable search path is: ModLoad: 00000000`00400000 00000000`0048e000 image00000000`00400000 ModLoad: 00000000`77ec0000 00000000`77ffc000 ntdll.dll ModLoad: 00000000`6b000000 00000000`6b046000 C:\WINDOWS\system32\wow64.dll ModLoad: 00000000`6b280000 00000000`6b2ca000 C:\WINDOWS\system32\wow64win.dll ModLoad: 00000000`78b80000 00000000`78b89000 C:\WINDOWS\system32\wow64cpu.dll (8c.fa8): Break instruction exception - code 80000003 (first chance) *** ERROR: Symbol file could not be found. Defaulted to export symbols for ntdll.dll - ntdll!DbgBreakPoint: 00000000`77ef24f0 cc int 3 0:000> g ModLoad: 00000000`77d40000 00000000`77eb3000 NOT_AN_IMAGE ModLoad: 00000000`7d4c0000 00000000`7d5f0000 NOT_AN_IMAGE ModLoad: 00000000`7d600000 00000000`7d6f0000 C:\WINDOWS\SysWOW64\ntdll32.dll ModLoad: 00000000`77d40000 00000000`77eb3000 NOT_AN_IMAGE ModLoad: 00000000`77c20000 00000000`77d2c000 NOT_AN_IMAGE ModLoad: 00000000`7d4c0000 00000000`7d5f0000 C:\WINDOWS\syswow64\kernel32.dll ModLoad: 00000000`61000000 00000000`61480000 C:\cygwin\bin\cygwin1.dll ModLoad: 00000000`6fda0000 00000000`6fdaf000 C:\cygwin\bin\cygintl-8.dll ModLoad: 00000000`6fdb0000 00000000`6feac000 C:\cygwin\bin\cygiconv-2.dll ModLoad: 00000000`6fa70000 00000000`6fa9d000 C:\cygwin\bin\cygreadline7.dll ModLoad: 00000000`6fb20000 00000000`6fb61000 C:\cygwin\bin\cygncursesw-10.dll ModLoad: 00000000`6ff90000 00000000`6ffa8000 C:\cygwin\bin\cyggcc_s-1.dll ModLoad: 00000000`7d930000 00000000`7da00000 C:\WINDOWS\syswow64\USER32.dll ModLoad: 00000000`7d800000 00000000`7d890000 C:\WINDOWS\syswow64\GDI32.dll ModLoad: 00000000`7d1e0000 00000000`7d27c000 C:\WINDOWS\syswow64\ADVAPI32.dll ModLoad: 00000000`7da20000 00000000`7db00000 C:\WINDOWS\syswow64\RPCRT4.dll ModLoad: 00000000`7d8d0000 00000000`7d920000 C:\WINDOWS\syswow64\Secur32.dll (8c.fa8): WOW64 breakpoint - code 4000001f (first chance) First chance exceptions are reported before any exception handling. This exception may be expected and handled. *** ERROR: Symbol file could not be found. Defaulted to export symbols for C:\WINDOWS\SysWOW64\ntdll32.dll - ntdll32!DbgBreakPoint: 00000000`7d61002d cc int 3 0:000:x86> g SetContext failed, 0x8007001F MachineInfo::SetContext failed - Thread: 00000000002F16C0 Handle: 26c Id: fa8 - Error == 0x8007001F IUserDebugServices::ContinueEvent failed with status 0xD000000D No current thread in SetContext No current thread in SetContext WaitForEvent failed ?:???> .restart WARNING: The debugger does not have a current process or thread WARNING: Many commands will not work TerminateProcess failed, Win32 error 5 CommandLine: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/000-cygwin-post-install.sh" IUserDebugServices::ContinueEvent failed with status 0xD000000D WaitForEvent failed=
-- 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
