Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Jeff Harrell <jharrell@ti.com>
To: linux-mips@oss.sgi.com
Subject: Symbol generation with cross compiler tools
Date: Fri, 02 Jun 2000 08:50:00 -0600	[thread overview]
Message-ID: <3937C998.5CD7BE81@ti.com> (raw)

I would like to run a quick question past this news group. I am seeing
problems
with symbol generation on the mipsel cross compilation tools.  I am
using the XRAY debugger
with a Macgraigor EJTAG pod on a MIPS R4Kc (jade) core.  The XRAY
documentation says that it
should be able to recognize the symbols in an ELF executable.  The mips
tools (Cygnus GCC 2.9.x) that is
shipped with the development system has no problem generating symbols
that the XRAY debugger can recognize.  When I attempt to do  a similar
test with the SGI cross compiler tools, XRAY doesn't
recognize any of the symbols.  Here are the versions of the
cross-compiler tools that I am currently using...


       binutils-mipsel-linux-2.8.1-1
       egcs-mipsel-linux-1.0.3a-1
       egcs-c++-mipsel-linux-1.0.3a-1
       egcs-libstdc++-mipsel-linux-2.8.0-1
       egcs-objc-mipsel-linux-1.0.3a-1
       egcs-g77-mipsel-linux-1.0.3a-1


I am using the "-g" command to generate debugging information.

I appreciate any information that anyone might have on similar
situations.  Thank you in advance

Jeff Harrell

--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Jeff Harrell                    Work:  (801) 619-6104
Broadband Access group/TI
jharrell@ti.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

             reply	other threads:[~2000-06-02 14:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-02 14:50 Jeff Harrell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-06-02 20:28 Symbol generation with cross compiler tools Joan Eslinger

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=3937C998.5CD7BE81@ti.com \
    --to=jharrell@ti.com \
    --cc=linux-mips@oss.sgi.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