From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19886 invoked by alias); 11 Mar 2008 17:45:27 -0000 Received: (qmail 19875 invoked by uid 22791); 11 Mar 2008 17:45:26 -0000 X-Spam-Check-By: sourceware.org Received: from dessent.net (HELO dessent.net) (69.60.119.225) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 11 Mar 2008 17:45:09 +0000 Received: from localhost ([127.0.0.1] helo=dessent.net) by dessent.net with esmtp (Exim 4.50) id 1JZ8XC-0007UP-S6; Tue, 11 Mar 2008 17:45:07 +0000 Message-ID: <47D6C524.69AECE6F@dessent.net> Date: Tue, 11 Mar 2008 17:49:00 -0000 From: Brian Dessent Reply-To: gdb@sourceware.org X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) MIME-Version: 1.0 To: Taras D CC: gdb@sourceware.org Subject: Re: stack trace and breaking before crash References: <4024fa2d0803100747g289cf2abl248dbc80b007356a@mail.gmail.com> <4024fa2d0803100824t788d284cq438043063335c750@mail.gmail.com> <47D55B70.1FA6B10C@dessent.net> <4024fa2d0803110805ob860320i5684c361f388c80f@mail.gmail.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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/msg00120.txt.bz2 Taras D wrote: > What am I doing wrong here? I'd like to get this 'core' option working > as the other option starts gdb in a DOS command prompt, which prevents > you from using any other type of interface with gdb (emacs/gui/etc) 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. If you don't like the command prompt (note: not DOS!) you can easily write a simple wrapper executable that invokes whatever debugger you prefer... in fact you can put your debugger as the error_start parameter. The only catch is that error_start has to name a real executable, it can't name a script or interpreter or batch file. And you don't have control over the arguments passed, $1 is the path to the binary and $2 is the pid. Brian