Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Date: Thu, 28 Jun 2001 15:44:49 +0400 From: egor duda X-Mailer: The Bat! (v1.53 RC/4) Reply-To: egor duda Organization: deo X-Priority: 3 (Normal) Message-ID: <137415815931.20010628154449@logos-m.ru> To: Darius DOT Clynes AT cec DOT eu DOT int CC: cygwin AT cygwin DOT com Subject: Re: gdb readable core dumps? In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi! Thursday, 28 June, 2001 Darius DOT Clynes AT cec DOT eu DOT int Darius DOT Clynes AT cec DOT eu DOT 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 ' and it'll create file named '.core' containing core dump of process with 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 AT logos-m DOT 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/