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] |
Brian: Thanks. The output of what you mention below is: ===================================================================== Microsoft Windows [Version 6.0.6001] Copyright (c) 2006 Microsoft Corporation. All rights reserved. C:\Users\Administrator>c:\cygwin\bin\bash.exe -xc /etc/postinstall/00bash.sh.done 3 [main] bash 1500 _cygtls::handle_exceptions: Exception: STATUS_ACCESS_VIOLATION 405 [main] bash 1500 open_stackdumpfile: Dumping stack trace to bash.exe.stackdump 444728 [main] bash 1500 _cygtls::handle_exceptions: Exception: STATUS_ACCESS_VIOLATION 461471 [main] bash 1500 _cygtls::handle_exceptions: Error while dumping state (probably corrupted stack) C:\Users\Administrator>type bash.exe.stackdump Exception: STATUS_ACCESS_VIOLATION at eip=0043AE30 eax=00000000 ebx=00000000 ecx=61106EC8 edx=00000000 esi=611021A0 edi=0045A3E0 ebp=0022CC68 esp=0022C62C program=c:\cygwin\bin\bash.exe, pid 1500, thread main cs=001B ds=0023 es=0023 fs=003B gs=0000 ss=0023 Stack trace: Frame Function Args 0022CC68 0043AE30 (00000003, 00F60D80, 00F60090, 61168990) 0022CD68 610060D8 (00000000, 0022CDA0, 61005450, 0022CDA0) 61005450 61004416 (0000009C, A02404C7, E8611021, FFFFFF48) 444728 [main] bash 1500 _cygtls::handle_exceptions: Exception: STATUS_ACCESS_VIOLATION 461471 [main] bash 1500 _cygtls::handle_exceptions: Error while dumping state (probably corrupted stack) C:\Users\Administrator> ====================================================================== I installed this system fresh today from the released version with only the default packages selected. When I run it under strace appear to fail pretty early but I have yet to try to dig deep there yet. I've attached the strace for reference. Let me know if there anything else I can do here to help analyze this. The strace output was simply a "bash --version" run, so it's not dependent on the script as it never gets there (as I noticed when I tried to slip in a "set -x" into the postinstall script before it was run...). Thanks, -- Eric ----- Original Message ---- From: Brian Dessent <brian@dessent.net> To: Eric Berge <emberge@yahoo.com> Cc: cygwin@cygwin.com Sent: Tuesday, May 27, 2008 10:18:03 AM Subject: Re: Problems installing on vista, no /bin in path Eric Berge wrote: > I tried to find out why the postinstalls failed but my current situation > is that bash is in the "segfault mode" and thus the scripts fundamentally > cannot run. I'll look for other ways of identifying why bash is segfaulting > but any recommendations would be welcome. Otherwise I'll keep plugging > away and let you know if I find anything new. When it segfaults it should produce some output as well as a bash.exe.stackdump file. What is the exact output of opening a command prompt and running "x:\whatever\path\to\bash.exe -xc /etc/postinstall/some-postinst-script-that-fails.sh"? Can you reduce it down to a simplest testcase that segfaults? Brian
Attachment:
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/
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |