From: "John M. Aldrich" <fighteer AT cs DOT com>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: DJGPP core dumps?
Date: Wed, 09 Jul 1997 19:20:11 +0000
Organization: Two pounds of chaos and a pinch of salt
Lines: 28
Message-ID: <33C3E46B.7FBC@cs.com>
References: <199707091429 DOT HAA13612 AT adit DOT ap DOT net>
Reply-To: fighteer AT cs DOT com
NNTP-Posting-Host: ppp108.cs.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

Nate Eldredge wrote:
> 
> Are there any plans to have DJGPP do core dumps on SIGSEGV, etc, for
> postmortem debugging? I find that a helpful feature on Linux.

Core dumps are a Unix-specific bug.  Oops, I mean feature.  ;)

The crash traceback displayed on the screen when djgpp programs crash is
usually enough to diagnose the problem, if you use the proper tools. 
Make sure your program is compiled with the '-g' switch to provide full
debugging information, and then run the 'symify' program with your
executable as the parameter when the crash traceback is still on the
screen.  You can use the '-o' switch with symify to redirect the output
to a file.  This will tell you exactly where your program crashed, so
you can go there and find the bug.

If more detailed debugging is needed, simply run your program under
gdb.  It should run identically but when the crash occurs you will be
able to see the exact status of all variables, etc.  Or you can use
RHGDB, the builtin Turbo-C style debugger of RHIDE.

-- 
---------------------------------------------------------------------
|      John M. Aldrich       |"Men rarely (if ever) manage to dream |
|       aka Fighteer I       |up a god superior to themselves. Most |
|   mailto:fighteer AT cs DOT com   |gods have the manners and morals of a |
| http://www.cs.com/fighteer |spoiled child."    - Lazarus Long     |
---------------------------------------------------------------------