Message-Id: <3.0.1.32.20010329131333.006a809c@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: Thu, 29 Mar 2001 13:13:33 +0800 To: djgpp-workers AT delorie DOT com From: "Nimrod A. Abing" Subject: Re: dpmiexcp.c with core dumping Cc: eliz AT is DOT elta DOT co DOT il In-Reply-To: <200103281735.MAA05011@envy.delorie.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" 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 At 12:35 PM 03/28/2001 -0500, you wrote: > >> 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 > >I don't know the gdb side, but the key is that bfd needs to be able to >read the core file. > >> In particular, I don't really understand why does the core file needs >> to be COFF. > >It can be anything, as long as bfd and gdb can use it. PMDBCD it is then? I've been reading the BFD docs and I've managed to grok a few important things in the process. All one has to do to enable BFD to read another binary file format is to write backend functions that can read the format and include it with the BFD library. This has to be done by the one working on the GDB/BFD side. Sound simple enough, eh? But I guess writing an API to read the current format would be simpler as Eli suggests. Unless one would really want to debug a DJGPP program using a GDB for Linux, All I've to do now is restructure the core file to suit the BFD structure. nimrod_a_abing -------------- +========================================+ | Home page: www.geocities.com/n_abing | +========================================+ "Tinimbang ka ngunit kulang." If you understand that phrase, i-email mo'ko. ;-)