From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-32184-listarch-gdb=sources.redhat.com@sourceware.org>
Received: (qmail 10941 invoked by alias); 23 Jun 2008 18:23:26 -0000
Received: (qmail 10891 invoked by uid 22791); 23 Jun 2008 18:23:25 -0000
X-Spam-Check-By: sourceware.org
Received: from mtaout2.012.net.il (HELO mtaout2.012.net.il) (84.95.2.4)     by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 23 Jun 2008 18:23:06 +0000
Received: from HOME-C4E4A596F7 ([84.229.217.57]) by i_mtaout2.012.net.il (HyperSendmail v2004.12) with ESMTPA id <0K2X00L4DIFR6LP2@i_mtaout2.012.net.il> for gdb@sourceware.org; Mon, 23 Jun 2008 21:38:16 +0300 (IDT)
Date: Mon, 23 Jun 2008 18:23:00 -0000
From: Eli Zaretskii <eliz@gnu.org>
Subject: Re: How to catch GDB crash
In-reply-to: <1214241124.3601.1180.camel@localhost.localdomain>
X-012-Sender: halo1@inter.net.il
To: Michael Snyder <msnyder@specifix.com>
Cc: divis1969@mail.ru, gdb@sourceware.org
Reply-to: Eli Zaretskii <eliz@gnu.org>
Message-id: <ubq1sf1tk.fsf@gnu.org>
References: <E1KAoxN-0001HF-00.divis1969-mail-ru@f132.mail.ru> <1214241124.3601.1180.camel@localhost.localdomain>
X-IsSubscribed: yes
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
X-SW-Source: 2008-06/txt/msg00221.txt.bz2

> From: Michael Snyder <msnyder@specifix.com>
> Cc: gdb@sourceware.org
> Date: Mon, 23 Jun 2008 10:12:04 -0700
> 
> You're running on a Windows host, right?  Doesn't Windows have
> some mechanism for automatically catching a program that is
> crashing, and holding it for the debugger?

That's true, but you need special code in the debugger to be able to
work like that (it's called JIT debugging, btw).  And GDB doesn't
(yet) have such code.