Date: Thu, 10 Jul 1997 17:04:10 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Andrew Crabtree <andrewc AT typhoon DOT rose DOT hp DOT com>
cc: fighteer AT cs DOT com, djgpp AT delorie DOT com
Subject: Re: DJGPP core dumps?
In-Reply-To: <199707101351.AA237182714@typhoon.rose.hp.com>
Message-ID: <Pine.SUN.3.91.970710170112.20363D-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk


On Thu, 10 Jul 1997, Andrew Crabtree wrote:

> Sure, if it happens while you, the designer are running the 
> program.  But I really don't want to have to distribute simify with
> any beta type software and have people run that thenselves and 
> report back the info.  Here, a core dump would be much more useful.

If it is just a problem of making sure the info gets written to a file, 
you could easily install a handler for SIGSEGV (or change the default one 
in the library) so that the crash dump is written to a file.  Call that 
file `core' and you can pretend that you have this feature ;-).

The thing is, real core dumps have much more info that just the stack 
frames and the registers.