Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Mon, 29 Nov 2004 13:52:20 -0800
From: David Hinds <dhinds AT sonic DOT net>
To: Cygwin List <cygwin AT cygwin DOT com>
Subject: Re: A vexing installation problem
Message-ID: <20041129215220.GA15085@sonic.net>
References: <20041129071451 DOT GA15469 AT sonic DOT net> <6 DOT 2 DOT 0 DOT 14 DOT 0 DOT 20041129115158 DOT 046c9120 AT pop DOT prospeed DOT net> <20041129184442 DOT GA30302 AT sonic DOT net> <6 DOT 2 DOT 0 DOT 14 DOT 0 DOT 20041129135305 DOT 046bca10 AT pop DOT prospeed DOT net> <20041129195946 DOT GA4932 AT sonic DOT net> <6 DOT 2 DOT 0 DOT 14 DOT 0 DOT 20041129151309 DOT 046bfba0 AT pop DOT prospeed DOT net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <6.2.0.14.0.20041129151309.046bfba0@pop.prospeed.net>
User-Agent: Mutt/1.4.2i

On Mon, Nov 29, 2004 at 03:18:05PM -0500, Larry Hall wrote:
> At 02:59 PM 11/29/2004, you wrote:
> >The postinstall scripts are all cygwin shell scripts and thus require
> >a functional 'sh' to do anything.  And, as with all other cygwin
> >programs, 'sh' just exits without doing anything.  
> 
> 
> Yep, so I'd recommend starting there.  Check the Windows properties here
> to see who owns the file and who has permissions to execute it, etc.  Also,
> you could do a strace on 'sh' to see if anything interesting shows up from
> that.  Hopefully you'll see something interesting as a result.

File permissions appear ok as far as I can tell.  The 'strace' output
seems consistent with no permission problems; I'm able to execute all
commands, cygwin1.dll is found, and things run for a short while
before dying.

'strace sh.exe' looks like any other command I try:

  ...
  564  105230 [main] bash 3892 cygheap_user::ontherange: what 2, pw 0xA0510C8
  224  105454 [main] bash 3892 cygheap_user::ontherange: HOME is already in the environment /cygdrive/h
  756  106210 [main] bash 3892 sigproc_init: process/signal handling enabled(1001)
  365  106575 [main] bash 3892 __cygwin_lock_lock: threadcount 1. not locking
  304  106879 [main] bash 3892 __cygwin_lock_unlock: threadcount 1. not unlocking

and I'm back to the Windows command prompt at this point.  I thought
maybe there could be something odd in my environment, but deleting all
entries has no effect: I still see the exact same behavior with an
environment that consists, in its entirety, of "PATH=.".

By hunting around on the internet, I was able to find some old cygwin
versions to test.  With an old version of 'mount', I get normal output
with the 1.5.5-1 version of cygwin1.dll, but 1.5.6-1 behaves the same
as 1.5.11-1 and 1.5.12-1 (no output, exits following sigproc_init).

I see that the 1.5.6-1 release changed signal processing which seems
suggestive given that the last substantive output of 'strace' comes
when signal handling is enabled.

-- Dave

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