Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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, 13 Oct 2003 22:50:19 -0400
From: Christopher Faylor <cgf-rcm AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: setup hangs during postinstall
Message-ID: <20031014025019.GA31727@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <Pine DOT GSO DOT 4 DOT 56 DOT 0310131207550 DOT 791 AT eos>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.GSO.4.56.0310131207550.791@eos>
User-Agent: Mutt/1.4.1i

On Mon, Oct 13, 2003 at 12:22:12PM -0500, Brian Ford wrote:
>Since setup must be launched from explorer to hang, I set
>CYGWIN_DEBUG=cygpath in my system environment variables and rebooted.  To
>make sure it worked, I launched a bash under rxvt and did a "cygpath -S".
>Up popped the gdb cmd shell.  But, under setup, no dice.

Are you saying that there was no popup?  That would imply that CYGWIN_DEBUG
is not in the environment.  You could just hack on the code in dcrt0.cc to
automatically pop up a gdb when command line contains cygpath, as a temporary
measure, of course.

>cygpath hangs just like before.  The stack trace looks a little different.
>Note that I have not had time to hand decode the holes in the trace yet,
>but it looks to me like a startup problem before the CYGWIN_DEBUG
>handling code.  A "fork exec copy" problem maybe?  I know that's vague,
>but I think you know what I mean.

The stack trace below is from a process that is running cygpath not from cygpath
itself.

So, there should be another cygpath process which is stuck, as you say,
prior to the point where it has "acquired the pid".  You should be able
to see it with a "ps -W".

cgf

>(gdb) info threads
>  3 thread 213.0xb5  0x77f7645d in _system_dlls__ ()
>  2 thread 213.0xd3  0x77f67fc7 in _system_dlls__ ()
>* 1 thread 213.0xd7  0x77f6838b in _system_dlls__ ()
>(gdb)i
>#0  0x77f6838b in _system_dlls__ ()
>#1  0x77f1d06a in _system_dlls__ ()
>#2  0x61091027 in WFMO (nCount=3, lpHandles=0x1, fWaitAll=2147348480,
>    dwMilliseconds=4294967295)
>    at ../../../../cygwin/winsup/cygwin/sigproc.cc:1248
>#3  0x6109344b in spawn_guts(char const*, char const* const*, char const* const*, int) (prog_arg=0xa044050 "/usr/bin/cygpath.exe", argv=0xa044b88,

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