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
Message-Id: <199905102121.QAA02070@modi.xraylith.wisc.edu>
X-Authentication-Warning: modi.xraylith.wisc.edu: localhost.xraylith.wisc.edu [127.0.0.1] didn't use HELO protocol
To: cygwin-developers <cygwin-developers AT sourceware DOT cygnus DOT com>
cc: Mikey <jeffdb AT goodnet DOT com>
Subject: Re: new core files 
In-reply-to: Your message of "Mon, 10 May 1999 16:45:36 EDT."
             <19990510164536 DOT C28227 AT cygnus DOT com> 
Date: Mon, 10 May 1999 16:21:56 -0500
From: Mumit Khan <khan AT xraylith DOT wisc DOT EDU>

Chris Faylor <cgf AT cygnus DOT com> writes:
> On Mon, May 10, 1999 at 07:48:00PM +0000, Mikey wrote:
> >The reason that win32 doesn't support core dumps
> >is that it supports JIT debugging.
> 
> Didn't Egor's previous patch pretty much accomplish this?
> 
> Core files definitely have a use that is not encompassed by JIT debugging.


JIT is a good technology, but it's limited to interactive debugging as the
name says. I've had people email me 100MB core dumps and that was the only
way I could find certain problems that needed certain OS environment etc
that I just couldn't reproduce.

I believe JIT technology is capable of supporting these "post-mortem dumps",
but it's a lot of work to get it right.

I like core files. No wait, I hate core files ;-)

Regards,
Mumit