X-Spam-Check-By: sourceware.org
Message-ID: <44029922.436F4B7A@dessent.net>
Date: Sun, 26 Feb 2006 22:16:02 -0800
From: Brian Dessent <brian@dessent.net>
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: instructions on how to build core file.
References: <440291B3.5070106@it.to-be.co.jp>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Reply-To: cygwin@cygwin.com
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com

djh wrote:

> Does cygwin have a way to produce a core file that would be useful as a
> portmortem, using gdb?

Yes, set the error_start parameter of the CYGWIN environment variable to
call dumper.exe.  Or better, just set it to gdb and the debugger will be
launched when the fault occurs and attached the the faulting process. 
The details are in the users guide.

Brian

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/