X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=1.7 required=5.0 	tests=AWL,BAYES_00,BOTNET,SPF_PASS
X-Spam-Check-By: sourceware.org
Message-id: <4A522DA6.2090200@verizon.net>
Date: Mon, 06 Jul 2009 10:00:22 -0700
From: Jerry DeLisle <jvdelisle AT verizon DOT net>
User-Agent: Thunderbird 2.0.0.21 (X11/20090320)
MIME-version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Bash initialization w/cygwin-1.7 on NT4
References: <4A517753 DOT 6000800 AT verizon DOT net>  <4A517B99 DOT 9090303 AT gmail DOT com>  <20090706043216 DOT GA7958 AT ednor DOT casa DOT cgf DOT cx>  <20090706152114 DOT GA14932 AT ednor DOT casa DOT cgf DOT cx>
In-reply-to: <20090706152114.GA14932@ednor.casa.cgf.cx>
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7bit
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
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

Christopher Faylor wrote:
> On Mon, Jul 06, 2009 at 12:32:16AM -0400, Christopher Faylor wrote:
>> On Mon, Jul 06, 2009 at 05:20:41AM +0100, Dave Korn wrote:
>>> Jerry DeLisle wrote:
>>>> I am making the switch to 1.7.  I started with a clean windows (nt4)
>>>> environment and went through the usual run of setup-1.7 downloaded today.
>>>>
>>>> All appears fine, but bash does not get initialized.
>>>>
>>>> pwd is /usr/bin
>>>>
>>>> path is not set
>>>>
>>>> home directory is not created
>>>>
>>>> These are all taken care of nicely for the user with cygwin 1.5
>>>>
>>>> I think this is a bug unless I am missing something in the install process.
>>> This is symptomatic of a problem preventing the postinstall scripts
>> >from having run correctly, isn't it?  Have a look in your
>>> /var/log/setup.log* files, and see what happened to
>>> base-files-profile.sh.
>> I can actually duplicate this problem on my NT4 virtual machine.
>> Unfortunately, I won't have a lot of time to track this down next
>> week but I'll get to it if no one else beats me to it.
> 
> I just checked in a fix for this.  It was a pretty embarrassing bug.
> For some reason, I had decided that it was ok not to check the error
> return value from an Nt* system call.  At least it was an easy fix.
> 
> For the curious, I debugged it by doing this:
> 
> set CYWGIN=error_start:gdb
> 
> When gdb popped up, the stack trace led me straight to the problem.
> 
> I am generating a new snapshot now but, given the nature of the problem,
> I'm not entirely sure how to suggest using the snapshot to fix the
> problem.  I guess one thing you could do is just rerun all of the
> post-install scripts after installing the snapshot cygwin1.dll.
> 

Maybe this warrants a cygwin1.dll release.

I will try the manual process you suggested after I figure out how to get the 
snapshot and when it is available.

Jerry


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple