Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
X-Authentication-Warning: slinky.cs.nyu.edu: pechtcha owned process doing -bs
Date: Thu, 22 May 2003 23:52:32 -0400 (EDT)
From: Igor Pechtchanski <pechtcha@cs.nyu.edu>
Reply-To: cygwin@cygwin.com
To: luke.kendall@cisra.canon.com.au
cc: cygwin@cygwin.com
Subject: Re: Setup failures during mirrored install
In-Reply-To: <20030523023935.0882A34C53@nevin.research.canon.com.au>
Message-ID: <Pine.GSO.4.44.0305222349010.26092-100000@slinky.cs.nyu.edu>
Importance: Normal
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Luke,

I've explicitly set Reply-To: to point to the list.  Please make sure your
mailer honors that in the future.  Thanks.

More comments below.

On Fri, 23 May 2003 luke.kendall@cisra.canon.com.au wrote:

> On 22 May, Igor Pechtchanski wrote:
> >  Define "hung"?  100% CPU?  0% CPU?  What was on the screen at the time?
> >  Did setup react to Windows events (i.e., could you cancel it)?  Would you
> >  be willing to try a debug snapshot of setup, attach to it with gdb when it
> >  hangs, and post a backtrace for each thread?
>
> Sorry, I should have been clearer.
>
> I meant that setup's progress simply stopped.  I could still cancel it,
> so it was still responding to mouse events.  Also, the system CPU load
> was low, and the network traffic was low.

Sounds like it's waiting for some event in one of the threads, but no
other thread sent the event...  The backtraces should be more informative,
though.

> I'd be willing to try a debug snapshot.  I haven't used gdb to debug
> threads though.
>
> I assume I run ps and use the PID, not the WINPID to attach to?
> What are the commands to list threads, and attach to a thread?
>
> Or do you simply say "thread apply all where" ?
>
> luke

The debugging snapshot is available at <http://cygwin.com/setup-snapshots/>.
Just run gdb, attach to the Cygwin PID, and use "info threads" to list all
threads.  Then switch to each thread by using "thread <n>", where <n> is
the thread number, and use "where" or "bt" to get a backtrace.
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha@cs.nyu.edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor@watson.ibm.com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski
    '---''(_/--'  `-'\_) 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/