This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: 1.5.18-1 Segfault on setup postinstall


Hello,

I am still unable to install cygwin. As a summary:
( I have windows XP Sp2 up to date.)

1. I download the most recent version of setup.exe (now 2.510.2.2).
2. I execute using default install settings.
3. Setup.exe hangs at 98% "Installing /etc/postinstall/s00ash.sh"
4. I click cancel and receive the message "installation complete".

Please note that cygwin was working nicely on my machine until about 2 months ago. I dont know if it was a cygwin update or something else installed on my machine. I made a backup and deleted all traces of the old cygwin installation including registry entries to try and get it working.

I rely on cywin for many features (xfig, xv, open ssh, etc..) and I really need to get it working again. Any help would be greatly appreciated.


Thanks in advance,


Andrew



Andrew Comport wrote:

Eric Blake wrote:

I left the install running overnight....still no progress...



Part of your problem is explained by this:


Not Found: sh



/etc/postinstall/00ash.sh tries to set up a working /bin/sh. If that fails, then everything else is suspect.


Upon inspection It is bash.exe (called within 00ash.sh) which crashes. I have created a strace for bash.exe which I have attached as a file. I have been unable to decipher eactly where this crashes.


Please note that i have edited the file to replace my Firstname and Lastname to be Firstname and Lastname.


Apparently its not cygcheck that crashes but id.exe:

3 [main] id 2792 handle_exceptions: Exception: STATUS_ACCESS_VIOLATION
18910 [main] id 2792 open_stackdumpfile: Dumping stack trace to id.exe.stackdu
mp
garbled output from `id' command - no uid= found



Figuring this out might help. Can you run 'strace -o strace.out id' and attach strace.out to your reply, to see if something obvious in id.exe or cygwin1.dll is reading bad memory? You may also want to try reinstalling coreutils, in case id.exe is corrupt.

I have also checked my PATH and set it to the basic PATHs of windows only so as to make sure no similar commands are on the path (which didnt help).



While not exactly wrong to change your PATH just before running cygcheck, it is a bit counterintuitive since part of cygcheck's purpose is to diagnose PATH problems in your current PATH.


I actually tried both ways. One with a minimal PATH and one with everything. The cygcheck output was the one without altering the full path.



Thanks for you help so far,


Andrew



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


Attachment: strace.out
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/

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]