For testing, I went out of my way and installed a local x64 Windows
Server 2008 Datacenter machine. Apart from updating to SP2 plus all the
latest Microsoft patches and configuring to match my environment, I have
not changed anything else, nor did I install any third-party software.
Then I installed a Cygwin Base install using the latest setup.exe.
It went 100% well. No fails in postinstall scripts. An interactive
bash started just fine.
Then I removed every trace of Cygwin from the machine and installed
Terminal Services, which is known to interfere badly with Cygwin
applications which don't have the TS-awareness flag set in the PE/COFF
header. I also installed any
Then I installed a Cygwin Base install using the latest setup.exe.
It went 100% well. No fails in postinstall scripts. An interactive
bash started just fine.
http://dch.posterous.com/cygwin-dumps-core-on-windows-2008-r1sp2-on-ec
So, this muse-ing of yours is not correct.
To me this implies that the Amazon Cloud VMs have some BLODA installed
by default. I'm not going to check this voluntarily. I suggest that
somebody who wants to run Cygwin on such a machine investigates this
further, or just asks Amazon to fix this and hope for the best.
Corinna
Thanks Corinna. I've not got w2008 server datacenter version to
install so that's pretty useful correlation - there must be something
funny in the EC2 AMI builds.
Others have encountered this too blamed a Xen bug - not sure if this
is a good interpretation but I can confirm that msys also fails with a
similar issue.
http://article.gmane.org/gmane.comp.emulators.xen.devel/73667
http://developer.amazonwebservices.com/connect/message.jspa?messageID=163059tstart=0
All that aside, I have done some further testing to see what security
features that are disabled in Windows 7/Vista are enabled in WS2008
DC edition:
- disabling the annoying UAC
- disabling DEP via bcdedit.exe /set {current} nx AlwaysOff
- disabling SEHOP (MS kb956607)
- disabling ASLR (ref
http://www.google.com/search?q=aslr+moveimages+%2Bsite:microsoft.com)
After toggling these settings on a standard virtualised windows 7
enterprise, I can't replicate the crash either on those OS so am
assuming there's something else.
Any other suggestions from the list of things that would be worth trying?
The muse-ing will be tweaked to be clear that this bug is only on the
publically available EC2 install I'll see how I get on with asking
amazon for a fix.
For reference here is the event log entry generated by bash.exe -
0xc005 presumably being a memory access violation, another one
from sh.exe, and a similar one from cmd.exe which is clearly not
cygwin related.
Log Name: Application
Source:Application Error
Date: 8/13/2010 2:05:30 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: ip-0AC1368F
Description:
Faulting application bash.exe, version 0.0.0.0, time stamp 0x4a18506d,
faulting module unknown, version 0.0.0.0, time stamp 0x,
exception code 0xc005, fault offset 0x75ba9b89, process id 0xa3c,
application start time 0x01cb3a839fa7f602.
and a similar one in sh.exe provides this stack dump:
Exception: STATUS_ACCESS_VIOLATION at eip=77574381
eax= ebx=0040 ecx= edx= esi=00F800F0 edi=0027C7C4
ebp=0027C778 esp=0027C760 program=C:\cygwin\bin\sh.exe, pid 2432, thread main
cs=0023 ds=002B es=002B fs=0053 gs=002B ss=002B
Stack trace:
Frame Function Args
0027C778 77574381 (0013, 00F800F0, 0040, 0027C7C4)
00FB8770 610341EE (, , , )
3 [main] sh 2432 exception::handle: Error while dumping state
(probably corrupted stack)
Event Xml:
Event xmlns=http://schemas.microsoft.com/win/2004/08/events/event;
System
Provider Name=Application Error /
EventID Qualifiers=01000/EventID
Level2/Level
Task100/Task
Keywords0x80/Keywords
TimeCreated SystemTime=2010-08-13T01:05:30.000Z /
EventRecordID876/EventRecordID
ChannelApplication/Channel
Computerip-0AC1368F/Computer
Security /
/System
EventData
Databash.exe/Data
Data0.0.0.0/Data
Data4a18506d/Data
Dataunknown/Data
Data0.0.0.0/Data
Data/Data
Datac005/Data
Data75ba9b89/Data
Dataa3c/Data
Data01cb3a839fa7f602/Data
/EventData
/Event
I have also managed to get a similar symptom crash on windows own cmd.exe -
Log Name: Application
Source:Application Error
Date: 8/13/2010 3:00:41 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: ip-0AC1368F
Description:
Faulting application cmd.exe, version 6.0.6001.18000, time stamp
0x47919317, faulting module ntdll.dll, version 6.0.6002.18005, time
stamp 0x49e0421d, exception code 0xc005, fault offset
0x000468a7, process id 0x348, application
