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, 30 May 2003 17:49:09 +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: <20030530074910.1D9B434C59@nevin.research.canon.com.au> On 22 May, Igor Pechtchanski wrote: > > 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 . > Just run gdb, attach to the Cygwin PID, and use "info threads" to list all > threads. Then switch to each thread by using "thread ", where is > the thread number, and use "where" or "bt" to get a backtrace. I finally got a chance to get back to this problem. You'll be glad to know that it has simply gone away. I suspect there really was a problem with our local mirror (or the upstream one), and that updates to the mirror mean the problem no longer occurs. Thanks for the advice - and the latest Cygwin (especially "startx -- -rootless"), is better than ever! 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/