Date:	Wed, 28 Mar 2001 11:39:09 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	DJ Delorie <dj AT delorie DOT com>
cc:	djgpp-workers AT delorie DOT com
Subject:	Re: dpmiexcp.c with core dumping
In-Reply-To:	<200103280537.AAA30378@envy.delorie.com>
Message-ID:	<Pine.SUN.3.91.1010328113835.4337P-100000@is>
MIME-Version:	1.0
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

On Wed, 28 Mar 2001, DJ Delorie wrote:

> How difficult would it be for the module to create a COFF format core
> file, similar to what bfd/gdb already knows how to read?

Not very difficult, IMHO: Emacs already does something similar when it
dumps itself, so we could just lift the code from there.

> That would make it a lot easier to add core support to gdb later.

Could you or someone else please post a list of issues that need to be
solved/figured out in order to add core file support to GDB?  The info
in gdbint.texinfo is sketchy at best, and seems to imply that the bulk
of core file support is in BFD, but bfd.texinfo is mostly silent about
core files (all it does is list a couple of unimportant functions).

In particular, I don't really understand why does the core file needs
to be COFF.  If reading the core file is a target-side operation, all
we need is to provide a function that satisfies some API used by GDB
to read information from the core file, no?

- Raw text -