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: Fri, 23 May 2003 12:39:35 +1000 (EST) From: luke DOT kendall AT cisra DOT canon DOT com DOT au Subject: Re: Setup failures during mirrored install To: cygwin AT cygwin DOT com Cc: Igor Pechtchanski In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Message-Id: <20030523023935.0882A34C53@nevin.research.canon.com.au> 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. 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 -- 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/