From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-42417-listarch-gdb=sources.redhat.com@sourceware.org>
Received: (qmail 18109 invoked by alias); 6 Aug 2013 19:25:09 -0000
Mailing-List: contact gdb-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb.sourceware.org>
List-Subscribe: <mailto:gdb-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb/>
List-Post: <mailto:gdb@sourceware.org>
List-Help: <mailto:gdb-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-owner@sourceware.org
Received: (qmail 18029 invoked by uid 89); 6 Aug 2013 19:25:09 -0000
X-Spam-SWARE-Status: No, score=-2.9 required=5.0 tests=AWL,BAYES_05,KHOP_THREADED,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_NO,RCVD_IN_NIX_SPAM,RDNS_NONE,SPF_SOFTFAIL autolearn=no version=3.3.1
Received: from Unknown (HELO mtaout21.012.net.il) (80.179.55.169)    by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Tue, 06 Aug 2013 19:25:07 +0000
Received: from conversion-daemon.a-mtaout21.012.net.il by a-mtaout21.012.net.il (HyperSendmail v2007.08) id <0MR400100J8U4W00@a-mtaout21.012.net.il> for gdb@sourceware.org; Tue, 06 Aug 2013 22:24:59 +0300 (IDT)
Received: from HOME-C4E4A596F7 ([87.69.4.28]) by a-mtaout21.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0MR40011VJ9M3840@a-mtaout21.012.net.il>; Tue, 06 Aug 2013 22:24:59 +0300 (IDT)
Date: Tue, 06 Aug 2013 19:25:00 -0000
From: Eli Zaretskii <eliz@gnu.org>
Subject: Re: How to debug fatal exceptions on Windows?
In-reply-to: <2613537.P6K19m4un9@localhost>
To: =?utf-8?Q?Pawe=C5=82?= Sikora <pawel.sikora@agmk.net>
Cc: gdb@sourceware.org
Reply-to: Eli Zaretskii <eliz@gnu.org>
Message-id: <83pptqvcyz.fsf@gnu.org>
MIME-version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8BIT
References: <83y58evno4.fsf@gnu.org> <2613537.P6K19m4un9@localhost>
X-SW-Source: 2013-08/txt/msg00014.txt.bz2

> From: Paweł Sikora <pawel.sikora@agmk.net>
> Date: Tue, 06 Aug 2013 20:49:54 +0200
> 
> from the winapi level you can use AddVectoredExceptionHandler (winapi) to install custom exception filter
> at the first position in the chain. next, from the exception filter you can examine suitable ExceptionRecord->ExceptionCode,
> and examine ContextRecord for more details.
> 
> the easier way is to use http://code.google.com/p/backtrace-mingw/

Thanks, I will study these.  Emacs already have a backtrace facility,
so I guess only the exception analysis stuff needs to be upgraded.