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 AT dessent DOT net>
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: instructions on how to build core file.
References: <440291B3 DOT 5070106 AT it DOT to-be DOT co DOT jp>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Reply-To: cygwin AT cygwin DOT com
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT 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/