Date: Wed, 28 Mar 2001 01:58:21 -0500
Message-Id: <200103280658.BAA31140@envy.delorie.com>
X-Authentication-Warning: envy.delorie.com: dj set sender to dj AT envy DOT delorie DOT com using -f
From: DJ Delorie <dj AT delorie DOT com>
To: djgpp-workers AT delorie DOT com
In-reply-to: <3.0.1.32.20010328145635.006aa9b0@wingate>
	(n_abing AT ns DOT roxas-online DOT net DOT ph)
Subject: Re: dpmiexcp.c with core dumping
References: <3 DOT 0 DOT 1 DOT 32 DOT 20010328133149 DOT 006aec58 AT wingate>
 <3 DOT 0 DOT 1 DOT 32 DOT 20010328133149 DOT 006aec58 AT wingate> <3 DOT 0 DOT 1 DOT 32 DOT 20010328145635 DOT 006aa9b0 AT wingate>
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


If there's already a debugger, that's cool too.  Adding support to gdb
is a matter of creating a BFD for the core format, and telling gdb
that djgpp has core files.

My thoughts about COFF cores is that there are already many tools that
deal with COFF format (objdump, nm, gdb, etc) that it would seem a
natural choice, that's all.  But realistically, only gdb needs to be
able to read the file.