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:	<37616E1F.3D6D822B@vinschen.de>
Date:	Fri, 11 Jun 1999 22:14:23 +0200
From:	Corinna Vinschen <corinna AT vinschen DOT de>
X-Mailer:	Mozilla 4.6 [en] (WinNT; I)
X-Accept-Language:	de,en
MIME-Version:	1.0
To:	Chris Faylor <cgf AT cygnus DOT com>
CC:	cygwin-developers AT sourceware DOT cygnus DOT com
Subject:	Re: No more .core files
References:	<19990610224952 DOT A26687 AT cygnus DOT com> <3760C1E0 DOT 459A3D41 AT vinschen DOT de> <19990611111702 DOT B795 AT cygnus DOT com>

Chris Faylor wrote:
> 
> On Fri, Jun 11, 1999 at 09:59:28AM +0200, Corinna Vinschen wrote:
> >Chris Faylor wrote:
> >>
> >> I just changed the name of the files produced by cygwin from
> >> something.core to something.stackdump.  Hopefully this will help
> >> minimize some confusion and pave the way for true core files in the
> >> future -- once I finally get the assignment form from Egor.
> >
> >The something.stackdump files will die then? Good news.
> 
> Only if someone has selected that they want to have core files.
> 
> I think that the stackdump files are marginally useful.  They allow
> me to say "It's not cygwin's fault." pretty quickly by inspecting the
> address where a fault occurred.

I understand.

Assuming, Egor has signed, shouldn't this behaviour be controlled by
the CYGWIN variable e.g (no)core (no)dump?

I think, this would be useful and convenient options.

Corinna

- Raw text -