Mailing-List:	contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender:	cygwin-developers-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin-developers AT sourceware DOT cygnus DOT com
From:	Chris Faylor <cgf AT cygnus DOT com>
Date:	Tue, 11 May 1999 11:18:23 -0400
To:	Egor Duda <deo AT logos-m DOT ru>
Cc:	cygwin-developers <cygwin-developers AT sourceware DOT cygnus DOT com>
Subject:	Re: new core files
Message-ID:	<19990511111823.B659@cygnus.com>
References:	<37373761 DOT 753883 AT mail DOT goodnet DOT com> <5453 DOT 990511 AT logos-m DOT ru>
Mime-Version:	1.0
X-Mailer:	Mutt 0.95.3i
In-Reply-To:	<5453.990511@logos-m.ru>; from Egor Duda on Tue, May 11, 1999 at 10:52:44AM +0400

On Tue, May 11, 1999 at 10:52:44AM +0400, Egor Duda wrote:
>M> Wouldn't it be more appropriate for this platform
>M> to get gdb.exe to work correctly with JIT than
>M> to clutter up everyones disks with a bunch of
>M> core files that most people would have no
>M> idea how to use, or why they are getting them?
>
>I've already posted a patch to allow JIT debugging of cygwin apps with
>gdb. Core files are good to find out why in hell one of your daemons
>crashed at 03:00am and dragged all your system down at 03:05am.
>Actually, i intend to add support for jit debugging and core dumping
>in a uniform way. You would just specify through %CYGWIN% a program to
>run in a case of trap and application will try to start it (passing
>some   info   about   itself).   Will   this   program  be  gdb(jit),
>core-dumper(post-mortem), something else or nothing -- it's up to you.

That sounds perfect to me.

-chris

- Raw text -