Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Dan Towner <dant@picochip.com>
To: gdb@sources.redhat.com
Subject: New object file parser?
Date: Fri, 12 Jul 2002 09:02:00 -0000	[thread overview]
Message-ID: <3D2EFDE0.159BCF83@picochip.com> (raw)

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


             reply	other threads:[~2002-07-12 16:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-12  9:02 Dan Towner [this message]
2002-07-12  9:50 ` Jim Blandy
2002-07-12  9:55   ` Dan Towner
2002-07-12 10:11     ` Daniel Jacobowitz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3D2EFDE0.159BCF83@picochip.com \
    --to=dant@picochip.com \
    --cc=gdb@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox