This is the mail archive of the gdb@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

New object file parser?


Hi all,

I am porting gdb to a new processor architecture (embedded
multi-processor DSP). Currently, although we use gcc as our compiler, we
have a proprietary assembler and linker, which generate non-standard
object and executable files. Now, faced with the task of getting the
symbol table information from the object file through to gdb, is it
easier to:

 1) Write a new parser for BFD.

or

 2) Write a converter which generates a standard object file format from
our proprietary format.

Whichever route I take, which object file would be the easier to deal
with? From what I have seen, I think that a.out would be the best, but
is there anything simpler? 

Dan,

=============================================================================
Daniel Towner
picoChip Designs Ltd., Riverside Buildings, 108, Walcot Street, BATH,
BA1 5BG
dant@picochip.com
07786 702589


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]