X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
Date: Sat, 08 Jan 2005 22:17:01 +0200
From: "Eli Zaretskii" <eliz AT gnu DOT org>
Sender: halo1 AT zahav DOT net DOT il
To: djgpp AT delorie DOT com
Message-ID: <01c4f5bf$Blat.v2.2.2$2bf2af20@zahav.net.il>
Content-Transfer-Encoding: 7BIT
Content-Type: text/plain; charset=ISO-8859-1
X-Mailer: emacs 21.3.50 (via feedmail 8 I) and Blat ver 2.2.2
In-reply-to: <T2UDd.54475$nP1.6671@twister.socal.rr.com>
	(sam124 AT operamail DOT com)
Subject: Re: coredumps?
References: <20050108145011 DOT 60a71ea7 DOT lijon AT kymatica DOT com> <01c4f58f$Blat.v2.2.2$03ce59c0 AT zahav DOT net DOT il> <T2UDd.54475$nP1 DOT 6671 AT twister DOT socal DOT rr DOT com>
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

> From: "Samuel Lauber" <sam124 AT operamail DOT com>
> Date: Sat, 08 Jan 2005 16:41:23 GMT
> 
> >> Is it possible to generate coredumps when DJGPP-programs crashes?
> 
> > No (no one written the code to support that).
> Should someone do that?

Volunteers are welcome, as always.

> Once I had the idea of generating a C file containing a __dpmi_regs
> with the current state of the registers and compiling it...

It's not a good idea to invent a private format for core files.  It is
much better to use one of the existing formats, notably, ELF, because
then supporting such core files in GDB would be trivial.

> > The closest you can get to this is the traceback printed when the
> > program crashes.
> And if it hasn't scrolled off the screen yet, you can type (in
> this example the program is called `a.out' and I'm at a
> Bourne shell)
> 
> bash-2.06$ symify ./a.out

bfdsymify would be better than symify.  Also, if the traceback does
scroll off, one can redirect stderr to a file (e.g., using the `redir'
program supplied with DJGPP), and then run bfdsymify on that file.