public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Paul.Nickerson@desknetinc.com
To: cygwin@cygwin.com
Subject: Re: Postinstall Script Errors With Exit Code 128
Date: Fri, 31 May 2013 08:34:00 -0000	[thread overview]
Message-ID: <OF160D8D15.B9C70282-ON85257B7C.00239146-85257B7C.0023B02A@desknetinc.com> (raw)
In-Reply-To: <51A65C03.3050107@cygwin.com>

[-- Attachment #1: Type: text/plain, Size: 2591 bytes --]

> 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

[-- Attachment #2: cygwin-bash-windbg.txt --]
[-- Type: text/plain, Size: 3168 bytes --]

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=

[-- Attachment #3: Type: text/plain, Size: 218 bytes --]

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

  reply	other threads:[~2013-05-31  6:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <OFB98AFA0A.C98BEEC2-ON85257B79.006C2BC1-85257B79.006C532B@LocalDomain>
2013-05-29 16:28 ` Paul.Nickerson
2013-05-29 16:40   ` Larry Hall (Cygwin)
2013-05-29 19:35     ` Paul.Nickerson
2013-05-29 20:28       ` Larry Hall (Cygwin)
2013-05-31  8:34         ` Paul.Nickerson [this message]
2013-05-31 18:45           ` Larry Hall (Cygwin)
2013-05-28 21:15 Paul.Nickerson
2013-05-29  2:23 ` Larry Hall (Cygwin)

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=OF160D8D15.B9C70282-ON85257B7C.00239146-85257B7C.0023B02A@desknetinc.com \
    --to=paul.nickerson@desknetinc.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).