Message-Id: Comments: Authenticated sender is From: "Salvador Eduardo Tropea (SET)" Organization: INTI To: George Foot , djgpp AT delorie DOT com Date: Tue, 16 Jun 1998 10:52:04 +0000 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: Debugging information in COFF/EXE files In-reply-to: <6lvppo$onu$4@news.ox.ac.uk> Precedence: bulk George Foot wrote: > Are there any libraries or small programs that make use of all of the > debugging information in COFF files? I know about the syms module > (src/debug/common/syms.c IIRC) and GDB. > > At the moment I am using the syms module, but it does not support > location of local variables on the stack, among other things. I have > not been able to look at GDB because downloading such large sources is > impractical for me at the moment. > > As far as I can see, edebug32 and fsdb just use the syms module and do > not support reading of local variables. > > If it comes to the crunch and no suitable (small) library exists then > I'll make my own, but I don't want to reinvent the wheel. I think there isn't such a library. But I think is better if you use the libgdb code because even when COFF is the default for djgpp a lot of people is moving to STABS. So you'll need to write support for both ... and what if we use DWARF ;-) COFF encoding is evil, some time ago I did a simple program to interpret the debug information using the description that DJ have in your pages and beleive me the COFF format is crazy. I know gdb is bloated but the best is to use it. What's used by objdump? SET ------------------------------------ 0 -------------------------------- Visit my home page: http://set-soft.home.ml.org/ or http://www.geocities.com/SiliconValley/Vista/6552/ Salvador Eduardo Tropea (SET). (Electronics Engineer) Alternative e-mail: set-soft AT usa DOT net set AT computer DOT org ICQ: 2951574 Address: Curapaligue 2124, Caseros, 3 de Febrero Buenos Aires, (1678), ARGENTINA TE: +(541) 759 0013