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
X-Authentication-Warning:	slinky.cs.nyu.edu: pechtcha owned process doing -bs
Date:	Wed, 8 Oct 2003 14:51:06 -0400 (EDT)
From:	Igor Pechtchanski <pechtcha AT cs DOT nyu DOT edu>
Reply-To:	cygwin AT cygwin DOT com
To:	Hannu E K Nevalainen <garbage_collector AT telia DOT com>
cc:	cygwin AT cygwin DOT com
Subject:	RE: setup hangs during postinstall
In-Reply-To:	<NGBBLLIAMFLGJEOAJCCEGEAFDFAA.garbage_collector@telia.com>
Message-ID:	<Pine.GSO.4.56.0310081450040.15176@slinky.cs.nyu.edu>
References:	<NGBBLLIAMFLGJEOAJCCEGEAFDFAA DOT garbage_collector AT telia DOT com>
Importance:	Normal
MIME-Version:	1.0

On Wed, 8 Oct 2003, Hannu E K Nevalainen wrote:

> > From: Christopher Faylor
>
> > On Wed, Oct 08, 2003 at 12:27:22PM -0500, Brian Ford wrote:
> > >Christopher Faylor wrote:
> > >>On Wed, Oct 08, 2003 at 12:49:44PM -0400, Igor Pechtchanski wrote:
> > >>>This is a known bug (as a search of the recent archives would have
> > >>>shown).  People are investigating.  As a short term workaround, you can
> > >>>"mv /etc/postinstal/XFree86-bin-icons.sh{,.done}" and rerun setup.
> > >>
> > >>I sure wish I could duplicate this bug...
> > >>
> > >Well, I can.
> > >
> > >I've got an XP box running a current CVS compiled cygwin DLL,
> > >a current CVS compiled cygpath, and a just downloaded setup stuck
> > >reinstalling XFree86-bin-icons.  I attached gdb to cygpath and got the
> > >following.
> > >
> > >It looks to me like the stack is corrupted, but I'm probably just being
> > >naive.
> >
> > This is unfortunately a standard stack for a frame-pointerless function
> > (probably *WaitForMultipleWindowsEx).  The laborious way to find the
> > caller is to do something like a:
> >
> > x/200x $esp
> >
> > and then look for 0x6100xxxx addresses in the output, decoding them with
> > something like:
> >
> > l *0x61041234
> >
> > There will be some garbage on the stack so some 0x6100xxxx addresses will
> > not be useful.
> >
> > That's the only way I know of to deal with this.  If gcc produced dwarf2
> > output, we could use the CFI to get more accurate information about the
> > stack frame but that's not going to happen anytime soon.
>
>  This is how it looks for me, when I try to follow the description above...
> HTH (not really expecting it to) :-I
>
> This is W2K adv server, SP4+ as I've told before... last and latest of all
> cygwin packages - and setup2.416-1  (updated this evening from rcn.net)

Hannu,

Can you attach to a hanging cygpath process with strace and post the
output?
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha AT cs DOT nyu DOT edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor AT watson DOT ibm DOT com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski, Ph.D.
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster."  -- Patrick Naughton

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

- Raw text -