Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin@sources.redhat.com>
List-Help: <mailto:cygwin-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner@sources.redhat.com
Delivered-To: mailing list cygwin@sources.redhat.com
Date: Thu, 28 Jun 2001 15:44:49 +0400
From: egor duda <deo@logos-m.ru>
X-Mailer: The Bat! (v1.53 RC/4)
Reply-To: egor duda <cygwin@cygwin.com>
Organization: deo
X-Priority: 3 (Normal)
Message-ID: <137415815931.20010628154449@logos-m.ru>
To: Darius.Clynes@cec.eu.int
CC: cygwin@cygwin.com
Subject: Re: gdb readable core dumps?
In-Reply-To: <A7AF87D6496DD411B50A00D0B76DEB2C1E6F4A@EX2BEBREYMBX02>
References: <A7AF87D6496DD411B50A00D0B76DEB2C1E6F4A@EX2BEBREYMBX02>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi!

Thursday, 28 June, 2001 Darius.Clynes@cec.eu.int Darius.Clynes@cec.eu.int wrote:


DCcei> Is it possible to have crashing processes produce a core dump
DCcei> which can then be read by gdb?

yes. cygwin includes special utility called dumper.exe which can be
used to create core dumps. run it with

'dumper <pid>'

and it'll create file named '.core' containing core dump of process
with pid '<pid>'. resulting dump can be inspected with gdb.

you can also make cygwin to start it automatically in case of fatal
error in application. add

'error_start=c:\path\to\dumper\utility\dumper.exe'

to your CYGWIN environment variable. 'error_start option turns on
cygwin's JIT debugging facility and allows running any program (dumper
or gdb) in case of crash in application.

in case of problems you can also search mailing list archives. they
contains several threads regarding core dump support in cygwin.

Egor.            mailto:deo@logos-m.ru ICQ 5165414 FidoNet 2:5020/496.19


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/