Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "H . J . Lu" <hjl@lucon.org>
To: Gerald Champagne <gerald.champagne@esstech.com>
Cc: "linux-mips@oss.sgi.com" <linux-mips@oss.sgi.com>
Subject: Re: Debugging symbols from gcc
Date: Thu, 4 Oct 2001 12:41:47 -0700	[thread overview]
Message-ID: <20011004124147.A16407@lucon.org> (raw)
In-Reply-To: <3BBCBB6B.6080809@esstech.com>; from gerald.champagne@esstech.com on Thu, Oct 04, 2001 at 02:41:31PM -0500

On Thu, Oct 04, 2001 at 02:41:31PM -0500, Gerald Champagne wrote:
> I'm trying to use a Wind River VisionProbe debugger with the
> Linux kernel, but I can't get the compiler to generate the symbols
> in the proper format.  The debugger works with an old compiler
> that places the symbols in sections called ".stab" and ".stabstr".
> It doesn't work with the newer compiler that places the symbols
> in a section called ".mdebug" (which I think is specific to sgi).
> 
> The version that creates .stab/.stabstr sections is:
> $ /usr/local/sde4/bin/gcc --version egcs-2.90.23 980102 (egcs-1.0.1 release)
> 
> The version that creates .mdebug sections is:
> $ /usr/bin/mips-linux-gcc --version egcs-2.91.66
> 
> Is there a way to specify the output format of the debug symbols?  I've
> seen documentation that references a -gstabs option, but that doesn't
> seem to work.  Should I be using a different version of the compiler?
> I'm just using the rpm's that were on the sgi site.
> 

I have fixed it in the current binutils and gcc. Those in RedHat 7.1
for mips should be ok. At least, I can use gdb 5.1 on the Linux
kernel.


H.J.

      reply	other threads:[~2001-10-04 19:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-04 19:41 Debugging symbols from gcc Gerald Champagne
2001-10-04 19:41 ` H . J . Lu [this message]

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=20011004124147.A16407@lucon.org \
    --to=hjl@lucon.org \
    --cc=gerald.champagne@esstech.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