From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26480 invoked by alias); 6 Aug 2013 16:07:19 -0000 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 Received: (qmail 26450 invoked by uid 89); 6 Aug 2013 16:07:18 -0000 X-Spam-SWARE-Status: No, score=-2.8 required=5.0 tests=AWL,BAYES_40,KHOP_THREADED,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_NO,RDNS_NONE,SPF_SOFTFAIL autolearn=no version=3.3.1 Received: from Unknown (HELO mtaout22.012.net.il) (80.179.55.172) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Tue, 06 Aug 2013 16:07:17 +0000 Received: from conversion-daemon.a-mtaout22.012.net.il by a-mtaout22.012.net.il (HyperSendmail v2007.08) id <0MR400L00A08SM00@a-mtaout22.012.net.il> for gdb@sourceware.org; Tue, 06 Aug 2013 19:07:07 +0300 (IDT) Received: from HOME-C4E4A596F7 ([87.69.4.28]) by a-mtaout22.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0MR400LNAA3UN450@a-mtaout22.012.net.il>; Tue, 06 Aug 2013 19:07:07 +0300 (IDT) Date: Tue, 06 Aug 2013 16:07:00 -0000 From: Eli Zaretskii Subject: Re: How to debug fatal exceptions on Windows? In-reply-to: <"000001ce92bb$ff059a60$fd10cf20$@muller"@ics-cnrs.unistra.fr> To: Pierre Muller Cc: gdb@sourceware.org Reply-to: Eli Zaretskii Message-id: <83vc3ivm4r.fsf@gnu.org> References: <83y58evno4.fsf@gnu.org> <"000001ce92bb$ff059a60$fd10cf20$@muller"@ics-cnrs.unistra.fr> X-SW-Source: 2013-08/txt/msg00012.txt.bz2 > From: "Pierre Muller" > Date: Tue, 6 Aug 2013 17:45:36 +0200 > > In fact, an exception is send first to the debugger, > then to the debuggee, and lastly again to the debugger if not handled by the > debuggee. > > But if GDB does not recognize the exception code, > it dies nothing on the first pass. > And the code is then caught by the gnu_exception_handler. > > > Did you try to run gdb on itself and > place a breakpoint on the location of the FirstChance code? If I do that, and the breakpoint breaks, how will I be able to see which code in the application (Emacs) caused the exception? Or did you mean something else? Thanks.