Date: Wed, 17 Jun 1998 09:04:26 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: "Salvador Eduardo Tropea (SET)" <salvador AT inti DOT gov DOT ar>
cc: George Foot <mert0407 AT sable DOT ox DOT ac DOT uk>, djgpp AT delorie DOT com
Subject: Re: Debugging information in COFF/EXE files
In-Reply-To: <m0ylw54-000S3zC@inti.gov.ar>
Message-ID: <Pine.SUN.3.91.980617085934.18792D-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk


On Tue, 16 Jun 1998, Salvador Eduardo Tropea (SET) wrote:

> I know gdb is bloated but the best is to use it. 
> What's used by objdump?

I believe both GDB and objdump use the BFD library to access the binary 
files in different format.

Btw, it is quite possible that by rearranging some of the GDB and/or BFD 
code you could make both GDB (in the DJGPP port) and any other code that 
needs to access the debug info, much smaller.  Currently, we are linking 
in a lot of BFD formats that are unsupported by DJGPP, like ELF, DWARF, 
and what's not.  Last time I asked Robert about this, he told me that 
removing those modules causes unresolved externals.  But those are 
probably artificial problems, and at the very least writing empty stubs 
for them will do.

I don't know if GDB 4.17 is any better in this respect.