I tried taking the latest snapshot and the failure still occurs. I also tried an alternative system which was running the 64-bit version of Win2008 and it failed in the same manner (so I've seen it on separate systems and on both 32-bit and 64-bit versions of Windows 2008).
Also I did something I should have some before, which was to run bash under strace. The output indicates bash is taking a SIGSEGV if I'm reading this correctly. This appears to occur immediately after calling "stat_worker", presumably to do a "stat" on "\??\C:\cygwin\tmp". The strace was from a 32-bit Win2008 box. I got the same profile in an strace from a 64-bit Win2008 box as well, although in that case the path was the "Unix" form of "/tmp". As before, any suggestions on how to take this analysis further are greatly appreciated. -- Eric ----- Original Message ---- From: Eric Berge <[EMAIL PROTECTED]> To: cygwin@cygwin.com Sent: Wednesday, May 21, 2008 11:20:24 AM Subject: Re: 1.5.25-11: Bash Fails after initial install on Windows 2008 Server I agree, as I have been able to get a couple of other Win2008 boxes to work (one was a 32-bit Win2008 and the other 64-bit Win2008). So the general capability is there, I expect I'm looking around for an odd sensitivity here. I'll give a try to a snapshot to see how that goes. Also, if anyone has anything else I can do to help diagnose this problem, please let me know what I should try. Thanks, Eric ----- Original Message ---- From: Corinna Vinschen <[EMAIL PROTECTED]> To: cygwin@cygwin.com Sent: Wednesday, May 21, 2008 2:11:22 AM Subject: Re: 1.5.25-11: Bash Fails after initial install on Windows 2008 Server On May 20 20:02, Eric Blake wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > According to Eric Berge on 5/20/2008 9:52 AM: > | I installed cygwin today on a Windows 2008 (32-bit) server > > I don't have access to Windows 2008, so take my advice with a grain of > salt... > > Often, crashing apps are the sign of http://cygwin.com/acronyms/#BLODA. > But in your case, this line from the cygcheck output is telling: > > | > | Windows Longhorn/Vista (not yet supported!) Ver 6.0 Build 6001 Service > Pack 1 > > You may want to try a snapshot, to see if the eventual 1.7.0 will handle > your setup better. That's really just a left over in cygcheck in the 1.5 branch. After all, the main purpose of the -11 release was to get Cygwin working on Windows 2008. I don't know what's causing the crash but it's not a general inability of Cygwin 1.5.25-11 or -12 to run on 2008. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
bash.strace
Description: Binary data
-- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
