X-Spam-Check-By: sourceware.org Date: Wed, 20 Sep 2006 12:17:40 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: gdb attach to process to produce stacktrace Message-ID: <20060920161740.GA25688@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20060920144836 DOT GA23721 AT trixie DOT casa DOT cgf DOT cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.11 Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: 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 On Wed, Sep 20, 2006 at 08:06:11AM -0700, Hans Horn wrote: >Exactly, thread 1 is of interest. That's the reason why the code posted >switches to thread 1! I apologize for missing that but I did tell you that the stack trace would not be useful if the program was stopped in a Windows DLL, which it clearly is. cgf -- 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/