Message-Id: <3.0.1.32.20010307152430.006f5b64@wingate>
X-Sender: n_abing#ns DOT roxas-online DOT net DOT ph AT wingate
X-Mailer: Windows Eudora Pro Version 3.0.1 (32)
Date: Wed, 07 Mar 2001 15:24:30 +0800
To: djgpp AT delorie DOT com
From: "Nimrod A. Abing" <n_abing AT ns DOT roxas-online DOT net DOT ph>
Subject: Dumping memory for a running program to disk
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Reply-To: djgpp AT delorie DOT com

Hello.

I am currently testing/developing a core dumping facility for DJGPP
programs like on UNIX systems. I've already roughed out the details of what
should go into a core file to enable the DJGPP port of GDB to do
post-mortem debugging. Dumping the call frame traceback addresses and
register states to disk does not seem to be enough (although it is useful
for backtracing already) for full post-mortem debugging support.

Anyone with pointers/ideas/information? Basically what I need to do is dump
the contents of memory that is allocated to and allocated by a running
DJGPP program. This need not be the entire program itself as it is laid out
in core, only the relevant parts: cpu registers, stack frames, global vars,
environment vars, etc.

Currently, I've written some test programs that dump the environment state
as well as the call frame traceback to a binary file (for DJLSR203). I've
yet to decide on the layout of the ``core'' file so that GDB or other
debuggers can read it.

All DJGPP users interested in testing/developing this or those with
ideas/information that would be useful, please contact me by private mail.

TIA.


nimrod_a_abing
--------------

+========================================+
|  Home page: www.geocities.com/n_abing  |
+========================================+

"Tinimbang ka ngunit kulang."
If you understand that phrase, i-email mo'ko. ;-)