Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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: Wed, 15 Oct 2003 15:20:16 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: setup hangs during postinstall Message-ID: <20031015192016.GA7725@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20031015184121 DOT GC28402 AT redhat DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i On Wed, Oct 15, 2003 at 03:10:36PM -0400, Igor Pechtchanski wrote: >On Wed, 15 Oct 2003, Brian Ford wrote: > >> On Wed, 15 Oct 2003, Christopher Faylor wrote: >> >> > On Wed, Oct 15, 2003 at 07:24:53PM +0100, Steve Fairbairn wrote: >> > >As Brian has noted, Executing the binary with '< /dev/null' stops the >> > >hanging, but also executing it without capturing the output to a variable >> > >also stops the hanging. >> > >> > I would guess that something like >> > >> > foo=`bar` >> > >> > is what is causing the problem because this uses a pipe for >> > communication. In a shell that is run from setup.exe, it is possible >> > that stdin is not opened at all and stdout is the pipe in question. >> > Maybe this is somehow confusing the SHF* function. >> >> Yes. I thought this had always been clear. > >I'd say it's confusing the DLL initialization sequence, as the function >doesn't even have to be called (see the simple hanging example in this >thread). > >> Since this only happens in bash, and not in sh, I doubt that is the >> problem. Are we looking at some kind of weird bash bug here? We have >> almost eliminated most of Cygwin since MINGW SHLWAPI executables exhibit >> the problem. > >Speaking of which, what's the version of SHLWAPI that hangs? On my >machine (which doesn't exhibit the hang) I have > >$ ls -l shlwapi.dll msvcrt.dll >-rwxrwxr-x+ 1 Administ SYSTEM 300816 Oct 20 2000 shlwapi.dll >-rwxrwxr-x+ 1 Administ SYSTEM 290869 Oct 30 2001 msvcrt.dll > >The properties dialogs show the following versions: > >File version: 5.50.4522.1800 >Description: Shell Light-weight Utility Library >Copyright: Copyright (C) Microsoft Corp. 1981-2000 > >File version: 6.1.9359.0 >Description: Microsoft (R) C Runtime Library >Copyright: Copyright (C) Microsoft Corp. 1981-1999 -rwxrwxr-x+ 1 Administ SYSTEM 395264 Jul 13 16:05 shlwapi.dll Version 6.00.2800.1226 -rwxrwxr-x+ 1 Administ SYSTEM 286773 Jun 19 12:05 msvcrt.dll Version 6.00.2800.1226 Both are on a recently-updated Windows 2000 system. I can't duplicate the described problem. cgf -- 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/