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:	<19990611234044.2389.rocketmail@send205.yahoomail.com>
Date:	Fri, 11 Jun 1999 16:40:44 -0700 (PDT)
From:	Earnie Boyd <earnie_boyd AT yahoo DOT com>
Reply-To:	earnie_boyd AT yahoo DOT com
Subject:	Re: No more .core files
To:	cygwin-developers AT sourceware DOT cygnus DOT com
MIME-Version:	1.0

--- Corinna Vinschen <corinna AT vinschen DOT de> wrote:
> 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.

I agree.  However, display it to stdout if nocore and nodump.

Earnie.
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com

- Raw text -