From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22304 invoked by alias); 11 Mar 2008 17:49:30 -0000 Received: (qmail 22295 invoked by uid 22791); 11 Mar 2008 17:49:29 -0000 X-Spam-Check-By: sourceware.org Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 11 Mar 2008 17:49:06 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id D4DCF98140; Tue, 11 Mar 2008 17:49:04 +0000 (GMT) Received: from caradoc.them.org (22.svnf5.xdsl.nauticom.net [209.195.183.55]) by nan.false.org (Postfix) with ESMTP id B091B9811F; Tue, 11 Mar 2008 17:49:04 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.69) (envelope-from ) id 1JZ8b1-0003pn-Cn; Tue, 11 Mar 2008 13:49:03 -0400 Date: Tue, 11 Mar 2008 17:53:00 -0000 From: Daniel Jacobowitz To: gdb@sourceware.org Cc: Taras D Subject: Re: stack trace and breaking before crash Message-ID: <20080311174903.GA14722@caradoc.them.org> Mail-Followup-To: gdb@sourceware.org, Taras D References: <4024fa2d0803100747g289cf2abl248dbc80b007356a@mail.gmail.com> <4024fa2d0803100824t788d284cq438043063335c750@mail.gmail.com> <47D55B70.1FA6B10C@dessent.net> <4024fa2d0803110805ob860320i5684c361f388c80f@mail.gmail.com> <47D6C524.69AECE6F@dessent.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <47D6C524.69AECE6F@dessent.net> User-Agent: Mutt/1.5.17 (2007-12-11) X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2008-03/txt/msg00121.txt.bz2 On Tue, Mar 11, 2008 at 10:45:08AM -0700, Brian Dessent wrote: > I don't think you're doing anything wrong. It looks like the JIT > debugger code in Cygwin and/or dumper might need some bugfixes. The > reason that continuing works is that it simply retriggers the fault > again at the same location where it faulted the first time. Apparently > at the point where gdb and/or dumper attaches to the process, the > location of the fault is already lost and execution is somewhere inside > the ntdll bowels in the exception handling code. Try info threads? IIRC the debug connection is the "current" thread, and the app is otherwise in a suspended thread. -- Daniel Jacobowitz CodeSourcery