Message-Id: <199808130752.IAA27163@sable.ox.ac.uk>
Comments: Authenticated sender is <mert0407 AT sable DOT ox DOT ac DOT uk>
From: "George Foot" <george DOT foot AT merton DOT oxford DOT ac DOT uk>
To: "Gurunandan R. Bhat" <grbhat AT unigoa DOT ernet DOT in>
Date: Thu, 13 Aug 1998 08:51:29 +0000
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re: [grbhat AT unigoa DOT ernet DOT in: Problem with process_coff()]
Reply-to: george DOT foot AT merton DOT oxford DOT ac DOT uk
CC: djgpp-workers AT delorie DOT com
Precedence: bulk

On 13 Aug 98 at 3:20, Gurunandan R. Bhat wrote:

> On Thu, 13 Aug 1998, George Foot wrote:
> 
> > If you'd find it useful to browse the COFF information fairly raw, I 
> > wrote a COFF dumper a while ago, which writes out the debugging 
> > information, partially translated into English.  In any case it might 
> > serve as a base to write something you'd find more useful.
> 
> I am interested and be happy to have a look at the sources if that's OK 
> with you

I've uploaded it to http://users.ox.ac.uk/~mert0407/coff.c.  Just
compile it as normal; it doesn't need `-ldbg'.  When you run it,
pass it the name of a COFF or EXE file on the command line, and it
will dump the information to stdout.  If you don't pass a filename
it will dump its own information.

It only dumps the symbol table information, not the line numbers,
but the line numbers are fairly easy to work with so you should be
able to add that if you need it.  In case you haven't found it
already, there's a reference to djgpp's COFF format somewhere at
http://www.delorie.com/djgpp/.

-- 
george DOT foot AT merton DOT oxford DOT ac DOT uk